How difficult can it be to have a "memory browser" o something like it, to tell us the state of our image and do nicely the script loader cleaning stuff?
I have no time now... but it would be nice. On Tue, Nov 16, 2010 at 2:10 PM, Mariano Martinez Peck < [email protected]> wrote: > > > On Tue, Nov 16, 2010 at 8:49 AM, Facundo Vozzi <[email protected]>wrote: > >> Hi Hernan, >> I did ScriptLoader new cleanUpForRelease on my fat image and It's 31 MB >> again. There is black magic in cleanUpForRelease :-P. >> > > Yes check it's implementation. I think the biggest black magic is the MC > history. > BTW, maybe we should add Transcript log to show each statement the amount > of memory that is released? or something like that.... > > cheers > > mariano > > >> >> Thanks, >> Facu >> >> >> On Tue, Nov 16, 2010 at 1:47 AM, Hernán Morales Durand < >> [email protected]> wrote: >> >>> Hi Facundo, >>> >>> Which Pharo version are you using? >>> >>> Try, >>> >>> ScriptLoader new cleanUpForRelease. >>> >>> I'm working with Seaside, Magma, XML, WebClient, VMMaker, OB, Glamour, >>> Mondrian, etc. plus my own projects and image size is 30Mb >>> Cheers, >>> >>> 2010/11/16 Facundo Vozzi <[email protected]>: >>> > Hi, >>> > I have one of my development pharo image with 103 MB of size. Is there >>> an >>> > normal image size on Pharo? I clean my system orphan instances and >>> > WARegistry clearAllHandlers but it continue with that size. >>> > There is on Pharo any tool like to Space Breakdown Chris Upal Dolphin >>> > Package (http://metagnostic.dolphinmap.net/SpaceBreakdown.html)? >>> > Thanks you, >>> > Facundo >>> >>> >>> >>> -- >>> Hernán Morales >>> Information Technology Manager, >>> Institute of Veterinary Genetics. >>> National Scientific and Technical Research Council (CONICET). >>> La Plata (1900), Buenos Aires, Argentina. >>> Telephone: +54 (0221) 421-1799. >>> Internal: 422 >>> Fax: 425-7980 or 421-1799. >>> >>> >> >
