Yes, there are clearly objects lying around. I suspect it has to do with Playground or Inspector, but I am not sure.Doru--On Tue, Mar 24, 2015 at 4:13 PM, Max Leske <maxleske@gmail.com> wrote:
> On 24 Mar 2015, at 15:18, Sven Van Caekenberghe <sven@stfx.eu> wrote:
>
> Hi,
>
> There seems to be some kind of memory leak in recent Pharo 4.0 images. Image size (as saved on disk) seems to be growing very rapidly under normal use (development with Nautilus, Spotter, GTPlayground, GTInspector and Monticello, debugging). Numbers go from the initial 20Mb to 100s of Mb and they seem to increase constantly, over a period of days.
Are you saying that the static image size is growing? Dynamic growth could easily be explained by leaks in NativeBoost for instance. But static image size means that there are objects lying around that shouldn���t (at least that should be easier to debug).
>
> One way to look at memory use is with
>
>�� SpaceTally printSpaceAnalysis
>
> but that takes a while.
>
> Please help us find and fix this issue.
>
> Thanks,
>
> Sven
>
>