[PD] closed window not destroyed? (in l2ork, possibly in others too)

IOhannes m zmoelnig zmoelnig at iem.at
Wed Jun 19 09:23:36 CEST 2013

Hash: SHA1

On 2013-06-18 22:58, András Murányi wrote:
> Hi List,
> I've got used to putting my PC to sleep (aka hibernation) often
> lately. Now there is this behaviour of Pd that when you leave a
> patch open and put the computer to sleep, once it wakes up Pd will
> try to do everything it missed while the computer was sleeping, so
> the CPU goes 100% for quite a while. I suppose this is by design. 
> What I've just noticed using l2ork is that I had closed my patch
> before hibernating (in order to avoid the CPU boost when waking
> up), put the computer to sleep for a few hours, and when i woke it
> up, surprisingly the 100% CPU boost still happened - with only the
> main window and console open. This makes me think some things are
> not destroyed properly when a patch is closed. Any thoughts
> appreciated...

i'm experiencing the same, and have not found the reason, nor did i
come up with a nice way how to easily debug this problem without doing
time consuming suspend/resume cycles (at least you don't need to
*hibernate* the system, a simple *suspend* to RAM triggers the problem
as well).

my system (as always) is:
- - debian jessie/sid (x86_64)
- - pd-vanilla 0.43, 0.44 (most likely; i have only recently started to
use 0.44 on a regular basis)

personally i don't think that this is related to some improper cleanup
(as it also happens with minimal patches that do not really do
anything "on their own"), but rather that Pd is checking the (empty?)
event-queue in tiny increments rather than one big go. or it might be
related to an overly simple watchdog logic.

but these are wild guesses.

Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/


More information about the Pd-list mailing list