[squeak-dev] Priority of WeakArray finalizationProcess

Joachim Geidel joachim.geidel at onlinehome.de
Sun Jun 13 07:55:38 UTC 2010


Am 12.06.10 21:47 schrieb Levente Uzonyi:
> On Sat, 12 Jun 2010, Joachim Geidel wrote:
>> I am not sure if changing the priority of the finalizationProcess could
>> possibly break something, and I also do not yet understand why changing the
>> priority makes such a big difference both in Squeak and Pharo.
> 
> I think normal processes (with priority 40) could starve the finalization
> process if it's priority were <= 40 (#systemBackgroundPriority is 20).

That's true, I hadn't thought of that.
 
>> How should this issue be handled? Should I add this as issues to the bug
>> tracking tools for Pharo and Squeak respectively?
> 
> I uploaded a fix to the Inbox: Collections-ul.362. If you're using a Trunk
> image, just update it and load this package to your image. If you're using
> a stock 4.1 image, then the easiest way to get the fix, is to add the
> following line to the end of WeakKeyDictionary >> #finalizeValues
> 
> cleanUpAfterRemove ifTrue: [ self fixCollisionsFrom: array size ]
> 
> If you have the time, please check if this fixes the issue for Squeak.

Unfortunately, this doesn't help with the deadlock issue.

Cheers,
Joachim Geidel





More information about the Squeak-dev mailing list