Hi, I did ScriptLoader new cleanUpForRealese on my pharo1.1.1 image and I get an index out of bounds error. Doing a debug, I found the source: a 0-length method category name on MCVersion class. So, I move all methods in that category to another and it just works (except for my image size that go from 95MB to 87MB :-). Cheers On Nov 16, 2010, at 14:10 , Mariano Martinez Peck wrote:
On Tue, Nov 16, 2010 at 8:49 AM, Facundo Vozzi <facundov79@gmail.com> 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 <hernan.morales@gmail.com> 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 <facundov79@gmail.com>:
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.