Well if it's a current mac/windows/linux VM then your image has  
attempted to allocate all  512MB of memory on mac, or I believe 1GB on  
windows and linux.
These limits are alterable, either on the command line, or in a plist.  
Operating system limits might dictate the upper limits here if the OS  
won't reach those values
or won't lie about those limits. What happens is that when memory  
actually runs low it signals the low space semaphore which triggers the  
"Space is low" warning.

If you do a help space left what does it say. Also do a help vm  
statistics. and report the results.

Either you have run out of memory and get this message, rare and  
usually quickly causes a lockup, or
you have attempted to pass some bogus very large value to new: which  
cannot be satisfiied. Hitting debug and
looking at the stack might tell you why and where you for example need  
500MB of memory?


On Dec 1, 2004, at 8:10 PM, Yar Hwee Boon wrote:

> I'm trying to access a particular object stored in GOODS and I'm  
> getting a "Space is low" warning. Any idea why? Thanks.
>
> --  
> Regards
> HweeBoon
> MotionObj
>
>
>
--
======================================================================== 
===
John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
======================================================================== 
===