print to stderr: does it make sense to redirect the error output to /dev/null - in oder to throw away everything that might clog up RAM ? $ sudo puredata -stderr 2>/dev/null
On 05 Dec 2018, at 15:26, michael strohmann itsnotfair9@gmail.com wrote:
Indeed i involuntarily write a lot to the console: i connect to an IP port every second via netsend (need to send status information to the lemur - app ) and netsend throws a message: netsend_connect: already connected
hopefully printing to stderr will solve this - thanks IOhannes!
would there be a way to tell netsend to only post more dramatic errors?
thanks anyway!!!
On 05 Dec 2018, at 15:14, IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 05.12.18 14:12, Christof Ressi wrote:
is sometimes piling up RAM, which causes the RPi to crash. can this be connected?
do you happen to print stuff to the console continuously? There was an issue that when you print *a lot* of text, the GUI would eventually run out of memory (don't know if this has been fixed in the meantime).
the question is how to actually fix it in a reasonable way. maybe I do want to have zillions of lines of text in my RAMmed up machine?
anyhow, if the printout is indeed the culprit (and it sounds like a plausible analysis to me), then a simpe fix could be to just print to stderr. that is, start pd with:
$ pd -stderr
you will still have a GUI, but the Pd-console will be redirected to the terminal (which just drops the oldest lines).
BTW: your last three e-mails all had different subject lines although the topic is the same. make sure that you keep the subject line, so people can later follow the thread.
+1, although you could have changed the subject as well :-)
very sorry! i was sending from webmail, which jumbled stuff up...
fgmr IOhannes
Pd-list@lists.iem.at mailto:Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list https://lists.puredata.info/listinfo/pd-list
-
michael strohmann