On Tue, Jun 10, 2008 at 9:20 AM, <bryce at kampjes.demon.co.uk> wrote:

> Andreas Raab writes:
>  > Of course, if I'd ever learn how to spell "timeout" correctly, I might
>  > find out that that's not the problem. Back to the drawing board... (but
>  > I'm still not convinced that the problem isn't somewhere in the nested
>  > unwind-protect stuff).
>
> It definately looks like it's caused by the changes to Delay>>wait.
>
>  wait
>        "Schedule this Delay, then wait on its semaphore. The current
>         process will be suspended for the amount of time specified
>         when this Delay was created."
>
>        self schedule.
>        [delaySemaphore wait] ifCurtailed:[self unschedule].
>
> If I comment out the "self unschedule" it works reliably. If I replace
> the "self unschedule" with "Processor yield" the bug occurs but takes
> a few more iterations (about 10 instead of 1 or two).
>


Is this bug recorded on bugs.squeak.org?

Gulik.

-- 
http://people.squeakfoundation.org/person/mikevdg
http://gulik.pbwiki.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20080611/30d21ad0/attachment.htm