Comment 10 for bug 565101

Yesterday night I bounced the whole rig (to start clean), and submitted a 2,000 instances run. Run ended at 03:30 UTC. Right now it is about 09:10 UTC, and the Walrus shows 1,166M of resident memory.

I am not sure how the garbage collection works, but it really does not look like it *is* working, or there is indeed a memory leak somewhere.