[Pharo-project] latest build yields stack trace running #cleanUpForProduction

Stéphane Ducasse stephane.ducasse at inria.fr
Wed Jan 18 08:30:02 CET 2012


Thanks.
Mariano I remember that with marcus we got the same impression: that the copyFrom: trick to avoid
a full scan was the cause of the trouble.
But I remember that you said that you had still a problem.

> Here's the fix:
> 
> I reverted MethodDictionary>>#compact to its previous version:
> 
> compact
> 	"Make sure that I have the highest possible load factor (at least 50%)."
> 	
> 	self become: self compactWithoutBecome
> 
> 
> The non-working version was:
> 
> compact
> 	"Make sure that I have the highest possible load factor (between 37.5% and 75%)."
> 	
> 	| newInstance |
> 	newInstance := self compactWithoutBecome.
> 	newInstance capacity = self capacity
> 		ifTrue: [ self copyFrom: newInstance ]
> 		ifFalse: [ self becomeForward: newInstance ]
> 
> After reverting, #cleanUpForRelease worked without problem.
> 
> 




More information about the Pharo-project mailing list