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 wrote:
>
> Indeed i involuntarily write a lot to the console:
> i connect
> +1, although you could have changed the subject as well :-)
guilty as charged
> Gesendet: Mittwoch, 05. Dezember 2018 um 15:14 Uhr
> Von: "IOhannes m zmoelnig"
> An: Kein Empfänger
> Cc: pd-list@lists.iem.at
> Betreff: Re: [PD] RPi Debug
>
> On 05.12.18 14:1
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
>
If you don't need the GUI and maybe even run the Raspberry Pi headless,
there is no need to run PD with it and the desktop at all, that way it
saves some CPU cycles even. PD can be started on commandline with the
parameter -nogui
We use that combination Raspberry Pi and PD i.e. as effect device in
Something's malfunctioning in Pd-watchdog.. but anyhow, is there any way you
can get Pd to run not as root? That way it has no way of kicking systemd
(which it somehow seems to be doing).
cheers
Miller
On Mon, Dec 03, 2018 at 02:11:07PM +0100, michael strohmann wrote:
> Hi,
> i don???t know if
Beloved List!
i am in the process of debugging a audio-installation that is running on a RPi
B+.
i noticed that the RPi restarted because it was running out of memory.
it seams that the pd-gui.tcl process i piling up memory and eventually crashes.
any hints on what could be the root of the proble
Hi,
i don’t know if i read this right: to me it looks like PD froze and the
watchdog sent SIGHUP. after which the system rebooted itself.
is there a way do find out why PD froze?
thanks!
michael
Dec 3 12:15:01 RoomOne CRON[3818]: (pi) CMD (ps aux --sort -rss|head -15 >>
/home/pi/Desktop/ps.lo
