Did you check on Dictionaries / Sets (+ their Identity* versions) and Symbols as well? Another possibility would non terminated Processes (process browser)? The Arrays themselves already look suspicious. Usually the way to track such objects down is to find and interesting candidate and inspect it, then right click and "explore strong pointers". I hope this helps On 2013-07-17, at 21:59, Paul DeBruicker <pdebruic@gmail.com> wrote:
I've been developing in the same Pharo2 image for a couple weeks and its now 180MB. I use the same development habits as in Pharo 1.4 but there the image would only be about 40MB.
Using SpaceTally I can see that I have 40 MB of Arrays. And 10MB of Bitmaps. 8MB of Floats, Strings, & OrderedCollections.
My domain objects comprise about 20MB of the image.
Is there a way to check for memory leaks over a long period of time?
Thanks
Paul