SharedQueue issues
John M McIntosh
johnmci at smalltalkconsulting.com
Fri Jun 17 02:36:58 UTC 2005
Well when I try this, it seems I avoid the deadlock between the two
semaphores, but then we trash the
ReadSync semaphore, or something certain happens.
Mind I'm wondering why we have special logic here to support
EventSensor queue logic, perhaps it should
be done in a different manner....
On 16-Jun-05, at 2:40 PM, John M McIntosh wrote:
> Sure try this piece of code on an image will need to force quit.
>
> | bad bad2 |
> bad _ [[Sensor flushNonKbdEvents] repeat] forkAt: Processor
> userBackgroundPriority.
> bad2 _ [[Sensor eventQueue peek] repeat] forkAt: Processor
> userBackgroundPriority.
>
> Execute this code above and click around in your image, it should
> dead-lock quite quickly.
> Haven't tried my solution to see if it works yet, exercise for the
> reader.
>
> On 16-Jun-05, at 6:55 AM, Chris Muller wrote:
>
>
>> Are you able to reproduce the deadlock easily?
--
========================================================================
===
John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com
========================================================================
===
More information about the Squeak-dev
mailing list
|