I am using TWM and yes it gobbles memory. Disable/GC/Enable is indeed aomething do every once in a while.
No need for snapshots for this to occur. A couple of Nautilus windows do the same. Youcan close them all in TWM and still have them eat memory. Phil Le 13 mai 2015 01:50, "Cameron Sanders via Pharo-users" < pharo-users@lists.pharo.org> a écrit : > > > ---------- Forwarded message ---------- > From: Cameron Sanders <camsand...@aol.com> > To: Any question about pharo is welcome <pharo-users@lists.pharo.org> > Cc: > Date: Tue, 3 Feb 2015 23:11:12 -0500 > Subject: Re: [Pharo-users] Image growing size > Do any of your (class/pool variable) singleton instances store data? add a > #clearAll or #reset (mySingletonVar := nil) to the class side -- or > whatever fits your app -- and do that before that #garbageCollect block. > [In fact, put that in some XXXAdmin class] > > Good Luck, > Cam > > On Tue, Feb 3, 2015 at 12:31 PM, p...@highoctane.be <p...@highoctane.be> > wrote: > >> Try to open monticello and select any repo, right click and clear the >> package cache. >> >> If you are using monticello that is. >> >> Also close all windows, open a workspace and do the >> >> 10 timesRepeat: [ Smalltalk garbageCollect]. >> >> HTH >> Phil >> Le 3 févr. 2015 17:49, "Laura Risani" <laura.ris...@gmail.com> a écrit : >> >>> Hi all, >>> >>> The official image i've downloaded weighted about 40 MB. Now its size is >>> about 200 MB. What is the explanation? Is this normal or have i done >>> something wrong? >>> >>> I haven't been using globals, just downloaded and defined some packages. >>> The only over persistent thing i've done is to keep an instance variable in >>> some classes i wanted to have a unique instance. >>> >>> >>> Best, >>> Laura >>> >> > >
