Hello, There could be many reasons why you would have such a big image.
The most common reason is the monticello metadata, as Phil said. Another reason could be because some caches and objects that are flushed on snapshot, so if you looked at the image size at runtime and not the file size (for example, the Display object, which is huge, is not in the snapshot, same thing for the AST cache) it is bigger. Another reason is that you may have kept persistent some data that refers to a huge graph of objects / a lot of objects. In the past, it happened to me that I kept errors in a collection to be able to debug them after the program execution (debugging directly the error would crash the image because it was errors in critical processes), but those errors were referencing a huge graph of nodes and after several thousands errors the image was overflowing its 1Gb limit. So what do you keep persistent in your application ? Does it refer to a lot of objects without you knowing it ? 2015-02-03 18:31 GMT+01:00 p...@highoctane.be <p...@highoctane.be>: > 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 >> >
