Hi,

to give some more information about the WeakArray finalization problem, 
here is a screenshot of a profiling-session in a 80 MB image running a 
big Seaside application:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: weakarray.gif
Type: image/gif
Size: 6428 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20041111/07ac8cf9/weakarray.gif
-------------- next part --------------


As far as I understand this means that during those 10 seconds we ran 
MessageTally, the finalization process bruned cpu cycles during 7 
seconds. There must be definitely something wrong, because we observed 
even stranger cases where ALL the cycles were spent there and the image 
became unresponsive. Of course we were not able to profile those, but 
this one is close and should give you a better idea about the problem.

Any ideas?

Thanks any hints,
Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch