I am running Squeak 3.1 (updated to latest updates) on Mandrake Linux 8.2. I'm finding that everything is fine after I set up an image, then a day or two later it seems to lock up and starts using 98% of the cpu.
Does anyone have any ideas about how I can avoid this?
Peter Robin Canberra Australia
Peter Robin peterr@netspeed.com.au wrote:
I am running Squeak 3.1 (updated to latest updates) on Mandrake Linux 8.2. I'm finding that everything is fine after I set up an image, then a day or two later it seems to lock up and starts using 98% of the cpu.
This might happen if you run out of memory. Does it lock up while you are using it, or while it is idle?
You can increase the memory using the -memory flag or the SQUEAK_MEMORY environment variable. (I increased the default on the SourceForge VM, because I seemed to not have a single image that could run happily in the old default.)
Incidentally, I tend to run Squeak for weeks without this kind of error. So, it can be done!
Lex
Peter Robin wrote:
I am running Squeak 3.1 (updated to latest updates) on Mandrake Linux 8.2. I'm finding that everything is fine after I set up an image, then a day or two later it seems to lock up and starts using 98% of the cpu.
Does anyone have any ideas about how I can avoid this?
Also, be sure to check the Squeak FAQ on the Swiki for some tips on what to do if you see a crash or a lock-up in Squeak.
http://minnow.cc.gatech.edu/squeak/2168
If you have additional tips which are not available in this FAQ item, be sure to add them.
- Doug Way Detroit, MI dway@riskmetrics.com
squeak-dev@lists.squeakfoundation.org
-
Doug Way -
Lex Spoon -
Peter Robin