[Pharo-project] Getting my head around low space

Schwab,Wilhelm K bschwab at anest.ufl.edu
Sat Oct 9 17:14:30 EDT 2010


You are probably way ahead of this (and keep pushing the envelope<g>), but you do know about #release, right?  A couple of weeks ago I ran some fairly intense calculations that resulted in low space conditions.  Sending #release to the participants (and implementing it correctly) fixed it.

One thing that IMHO has never worked well, or at least not as well as advertised, in Dolphin is relying on its finalization "water mark" to trigger cleanup of finalizable objects on need.  Most notably, I found it necessary to explicitly clean up ODBC statements to avoid errors/crashes.

How much memory do you need?  May I ask for what?  32 or 64 bit?


From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Max Leske [maxleske at gmail.com]
Sent: Saturday, October 09, 2010 12:01 PM
To: pharo-project at lists.gforge.inria.fr
Subject: [Pharo-project] Getting my head around low space


I'm having trouble with low space warnings in Pharo. Is there a source on how much memory the image can get from the OS? Is there maybe a way to up that limit? I am loading a lot of data into the image and the limit at the moment seems to be around 500 MB.

Thanks for any ideas.

Pharo-project mailing list
Pharo-project at lists.gforge.inria.fr

More information about the Pharo-dev mailing list