development image memory use: 180MB in Pharo 2 vs. 40MB in Pharo 1.4.....
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
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
On Jul 17, 2013, at 9:59 PM, 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.
I already saw that the current 3.0 download has 110.000 instances of array⦠I wondered if that makes sense.
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.
Can you run ImageCleaner cleanUpForRelease this calls e.g. all the #cleanUp methods of all classes. (We should think about how to call this (or a subset) more regularly in normal operation) Marcus
On Jul 18, 2013, at 8:04 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Jul 17, 2013, at 9:59 PM, 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.
I already saw that the current 3.0 download has 110.000 instances of array⦠I wondered if that makes sense.
We should have a look.
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.
Can you run
ImageCleaner cleanUpForRelease
this calls e.g. all the #cleanUp methods of all classes.
(We should think about how to call this (or a subset) more regularly in normal operation)
Marcus
thanks paul for the information. We should pay attention to this. May be we will have to have one release of Pharo focusing on not improving the libraries but its runtime behavior. The problem is that we need enough room to move and improve the infrastructure.
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.
Strange. We should check may be some memory leaks.
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
participants (4)
-
Camillo Bruni -
Marcus Denker -
Paul DeBruicker -
Stéphane Ducasse