[Pharo-project] InputEventFetcher starving all other processes

Stéphane Ducasse stephane.ducasse at inria.fr
Sun Oct 31 17:06:13 EDT 2010


what is strange is that pharo does not change the vm code.
One which OS are you?

> Hi:
> 
> On 31 Oct 2010, at 19:15, Stefan Marr wrote:
> 
>> But the symptoms are that InputEventFetcher>>primGetNextEvent: delivers 500-1000x more events than EventSensor>>primGetNextEvent: in MVC or Squeak 4.1 images deliver.
> Turns out that the array which is supposed to be filled in by '>>primGetNextEvent: array' does not get filled in correctly.
> For some reason the old values stay in the array when there isn't any new event.

may be a semaphore or something like that prevents some actions to happen. 
> 
> However, the very same code works for the non-Pharo images.
> 
> Was there any change to the code in or related to this primitive (<primitive: 94>) lately?
> 
> Thanks
> Stefan
> 
> 
> -- 
> Stefan Marr
> Software Languages Lab
> Vrije Universiteit Brussel
> Pleinlaan 2 / B-1050 Brussels / Belgium
> http://soft.vub.ac.be/~smarr
> Phone: +32 2 629 2974
> Fax:   +32 2 629 3525
> 
> 





More information about the Pharo-dev mailing list