Bugs item #2939290, was opened at 2010-01-25 06:51 Message generated for change (Comment added) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2939290...
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: puredata Group: None
Status: Pending
Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: pd eats all processor resources after suspend
Initial Comment: yes, its like that. pd eats all aviable processor resources after suspend until i close it. i have compiled version 0.42.5 without any errors on my ubuntu karmic (x64), using AMD Turion MK-36
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-01-26 18:33
Message: Cannot reproduce using Pd version 0.42.5-extended-20100120 on Mac OS X 10.5.8.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave) Date: 2010-01-26 18:33
Message:
An example patch is always very helpful, especially if it triggers the problem every time that it is run. Ideally the example patch would have only enough objects to cause the problem, but nothing else.
----------------------------------------------------------------------
Comment By: kubriel (kubriel) Date: 2010-01-25 11:45
Message: ok, i logged in. yes, but it is curious, why pd have to compute everything what had to be done during sleep? it sounds useless. i tried suspend my computer (for 5sec) with opened pd, but without opened patch, it happens again - eats all aviable cpu (until i kill the proces), but no patch opened.
----------------------------------------------------------------------
Comment By: Cyrille Henry (nusmuk) Date: 2010-01-25 07:32
Message: i can't reproduce this : pd 42.5 ubuntu karmic i386
however, after suspend, pd have to compute everything that as not been computed during suspend. so it can eat all cpu for some time, until it sync again with real time. this is only if a patch that use cpu is open during suspend.
----------------------------------------------------------------------
You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2939290...