<br><br><div class="gmail_quote">On Tue, Jun 10, 2008 at 9:20 AM, <<a href="mailto:bryce@kampjes.demon.co.uk">bryce@kampjes.demon.co.uk</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Andreas Raab writes:<br>
> Of course, if I'd ever learn how to spell "timeout" correctly, I might<br>
> find out that that's not the problem. Back to the drawing board... (but<br>
> I'm still not convinced that the problem isn't somewhere in the nested<br>
> unwind-protect stuff).<br>
<br>
It definately looks like it's caused by the changes to Delay>>wait.<br>
<br>
wait<br>
"Schedule this Delay, then wait on its semaphore. The current<br>
process will be suspended for the amount of time specified<br>
when this Delay was created."<br>
<br>
self schedule.<br>
[delaySemaphore wait] ifCurtailed:[self unschedule].<br>
<br>
If I comment out the "self unschedule" it works reliably. If I replace<br>
the "self unschedule" with "Processor yield" the bug occurs but takes<br>
a few more iterations (about 10 instead of 1 or two).<br>
</blockquote></div><br><br>Is this bug recorded on <a href="http://bugs.squeak.org">bugs.squeak.org</a>?<br><br>Gulik.<br clear="all"><br>-- <br><a href="http://people.squeakfoundation.org/person/mikevdg">http://people.squeakfoundation.org/person/mikevdg</a><br>
<a href="http://gulik.pbwiki.com/">http://gulik.pbwiki.com/</a>