[squeak-dev] Re: Sound latchup problem is back with
andreas.raab at gmx.de
Fri Apr 16 02:47:07 UTC 2010
On 4/15/2010 6:30 PM, Chris Muller wrote:
> Sorry for the late reply; but I have been fighting the same issue as
> Jerome; it's a pretty bad one. My code hit a Beep, something that
> should have taken one minute was still running after an hour (I
> suppose because the CPU was consumed but I didn't know that then).
> Attempting to profile ended up in a locked image (couldn't interrupt
> it with Alt+.).
> Toggling soundStopWhenDone seemed to fix the problem.
Did you try rc5? It has soundStopWhenDone set to true by default on Unix.
> Wow, I just was browsing senders of this method and noticed.. have a
> look at SmalltalkImage>>#snapshot:andQuit:embedded:. It calls
> #setPlatformPreferences which takes the trouble to force it true if
> booting into a Win32 environment, but false otherwise. Someone knows
> something about this..
Yeah, but for other reasons. In the old days, the sound device was an
exclusive resource and leaving open would prevent any other apps from
playing any sounds. CPU usage had little to do with it.
> On Wed, Apr 14, 2010 at 3:26 AM, Andreas Raab<andreas.raab at gmx.de> wrote:
>> On 4/14/2010 1:19 AM, Jerome Peace wrote:
>>> Derek>:There is a preference under "media" called
>>> "soundStopWhenDone" which, if enabled, stops the process when the sound
>>> queue is empty and brings CPU usage back down to normal.
>>> Well that seems to work. Can we get the image be released with this as the
>>> Or with this as the default for Linux/Ubuntu systems?
>> I'm willing to make this change if some Linux users can a) confirm that this
>> makes indeed a difference on their system and b) nobody reports a problem on
>> their Linux system. I will *not* touch it without feedback though, so Linux
>> users please test the preference and report back.
>> - Andreas
More information about the Squeak-dev