[squeak-dev] What are we leaking in the www.squeak.org process?

Colin Putney colin at wiresong.com
Wed Oct 20 07:16:11 UTC 2010


On Tue, Oct 19, 2010 at 10:35 PM, Ken Causey <ken at kencausey.com> wrote:


> I would really really appreciate some guidance here.

I'd assume that the VM is working fine, and something in the image is
what's using the memory. Try looking at counts of instances by class
and see if anything sticks out, then get a hold of one of them and
trace the references back and see where it's being referenced from.
Look at running Processes and see if there are any with odd things on
the stack that could reference a large tree of objects. Look at
Morphic: explore the World, the deferred messages queue and the ui
process.

Also look at the VM process from outside, via the OS. How many file
handles does it have open? What files, sockets, pipes etc do they
refer to? What shared libraries are loaded? Can you profile it and see
where it's spending most of its processing time? How do all these
things differ between a VM process that's just started, and one that's
been running a while and is using a lot of memory?

Just a few suggestions. Good luck!

Colin



More information about the Squeak-dev mailing list