I don't think it is incomplete freeing of patch resources based on what I saw so far. Could it be the watchdog's ping, isn't each of these tied to a specific timestamp? On Jun 19, 2013 3:50 AM, "Roman Haefeli" reduzent@gmail.com wrote:
On Tue, 2013-06-18 at 22:58 +0200, 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...
Does it help to toggle DSP off and on, when Pd is in this post-suspend mode? I had the impression it did, but I wasn't sure if it was just a coincident, that CPU usage stopped at the same moment.
Roman
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list