> On 25 Nov 2014, at 17:44, Hilaire <[email protected]> wrote: > > Le 25/11/2014 17:22, Esteban Lorenzano a écrit : >> For DrGeo2 I needed to expand that memory to 64m, but it was still in >> the reasonable numbers. >> > > How come so much? Image of latest built is below 10MB.
I’m talking by memory here, but I remember with “max memory” set to 32m I was having low memory warnings and I doubled it (no heuristics, it just looked “fine” to jump from 32 to 64 :P) and solved the problem. The problem could be happening in development images (before compaction)… but as I said, this was two years ago so I might be wrong. :P One thing to take into account is that memory management for pharo is/was not optimal, and VM could be asking for more memory than needed in certain circumstances. Other thing is that memory needed != memory of image. Of course, at the beginning it is, but you start creating/destroying objects right after, so your needs change. And well, there are tons other possible reasons, but in the case of DrGeo, I *think* (I don’t remember well) it was when rendering images (the predefined images: the screenshots when browsing examples, etc.). Esteban > > Hilaire > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > >
