On 25-Oct-05, at AM 08:58, William E Harford wrote:
On Mon, 2005-10-24 at 17:08 +0400, Dmitry Dorofeev wrote:
First trick is to start squeak in a 'safe' way. I.e. you must use
squeak -nodisplay -nosound -memory 64m your.image
If you dont limit memory usage, it may eat 100% of CPU and stop
responding.
Which is known UNIX VM bug as I get from the lists. Its related to
memory usage
over 1Gb.
This is super helpful. I was running into mysterious locking up of
Squeak. The image would just stop responding after a while and the only
thing that would fix it was restarting Squeak and sometimes having to
kill -9 it.
Maybe this should be added to the Seaside FAQ?
I'm not sure how to word this. I'll put it up if anyone can help to
write it :)
--
Hwee Boon
http://motionobj.com/blog/
MotionObj
(65) 6764-9774
| 
