memory leak problems
tim Rowledge
tim at rowledge.org
Fri Aug 5 22:18:30 UTC 2005
I'm not quite sure why but I have a faint suspicion that you might have
(cor, what a lot of weasel words for one sentence) a bunch of temp
variable bindings being held onto by your large workspace. You could
test this thesis by writing the contents out to a file and then closing
the workspace. GC a few times (Smalltalk garbageCollect ) and I think
you might find a lot of stuff gone.
Another place where a lot gets retained is the change sets - the old
versions of the out of date methods are kept, along with all the
literals etc. This is a bit different to the older changeset behaviour
where just the pointer to the source code was kept. In a COPY of your
image it might be worth trying destroying changesets and seeing how
much gets freed up.
tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
More information about the Squeak-dev
mailing list
|