Hi David -

> I'm cross-posting to Squeak-dev and I think this should migrate to that
> list (since it has come up there several times).  Please follow up to
> Squeak-dev only.  I don't believe this is a problem for VisualWorks
> which seems to have a significantly more robust weak reference mechanism.

True. From what I've seen over at the Seaside mailing list it seems 
pretty clear that the main issue is that the finalization process simply 
kicks in *way* to often. Have you guys (since you're having the problem 
I think it's appropriate if you can experiment with it a little ;-) 
thought about tweaking the finalization process to run at most (say) 
20/sec? This is a simple change (see attached CS) which could have 
dramatic impact on your performance. The obvious disadvantage, of 
course, is that this renders any assumptions about "Smalltalk 
garbageCollect" having an immediate effect meaningless (which is the 
main reason the finalization process is implemented the way it is).

> \begin{amateurHour}
[...]
> \end{amateurHour}

I'll reply to this separately.

Cheers,
   - Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FinalizationProcess.cs
Type: application/text
Size: 858 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20060324/87cf8608/FinalizationProcess.bin