In my message, archived here<br><a href="http://lists.squeakfoundation.org/pipermail/vm-dev/2007-October/001595.html">http://lists.squeakfoundation.org/pipermail/vm-dev/2007-October/001595.html</a><br>I mentioned that it seems that once a sound has played,
<br>the image keeps sending silence to the sound device.<br><br>This keeps the CPU quite busy, as seen both by the OS<br>(load average) and the interpreter (slower benchmarks).<br><br>I've had a little more time to dig into this, and it
<br>seems this is expected behaviour: it is toggled by the<br>"soundStopWhenDone" preference, and read in<br>SoundPlayer>>playLoop. It seems that this is<br>off by default (i.e. sound never really stops, once
<br>started). Switching it to "on" solved my problem.<br><br>So now I'm curious. Why was it built this way?<br>And why do released images have this preference off?<br><br>For most modern hardware, this isn't an issue, but for
<br>slower hardware (e.g. mine), or for power-lean systems<br>(e.g. the OLPC) I think it could be.<br><br>Andrew<br>