3.4 event system holding objects?

Bob Arning arning at charm.net
Sat Feb 8 10:26:18 UTC 2003


If events are responsible for keeping garbage around, then there are likely two reasons:

1. That events are implemented with strong references that need to be explicitly released, but are not.
2. The events are written in such a way as to carry extra baggage that might otherwise have been collected.

To see which of these might be behind the bloat you are seeing, it might help if you posted the result of one of your PointerFinder searches.


On Sat, 8 Feb 2003 02:33:45 -0500 "Bill Schwab" <schwabw at sprynet.com> wrote:
>I did a little more digging into that bloated image I mentioned a few 
>days ago.  First, I verified that I didn't have a large number of 
>lingering Process-es holding things in the image.  Then I did some 
>checking with the PointerFinder and it kept leading to events 
>associated with Wonderland actors (the objects that are most 
>notably lingering in the image).
>Some browsing in 3.4 (the problematic image) and my slightly 
>older 3.2 image reveals that my 3.4 image includes 
>Object>>when:evalaute, and that #when:send:to: and friends are 
>written in terms of it instead of #when:perform: as in 3.2.  I find this 
>suspicious because #when:evaluate: was removed from Dolphin 
>quite some time ago, specificially because it was causing 
>problems with large networks of objects that were immune to the 

More information about the Squeak-dev mailing list