I am not using any command line arguments.

I have 512Meg physical memory and 512Meg swap space (although even with
Squeak running, "top" says the none of the swap space is being used).

I think that I only started to see this issue when I upgraded from
256Meg physical memory to 512Meg, so maybe with Squeak having more
memory is not always a good thing!

After typing the above I just tried the -mmap 512M that you used.

In a couple of quick tests -mmap 512M fixes the problem for me but -mmap
1024M still fails. This would seem to be the opposite of what you found
but different machine, different OS(?) who knows.

Anyway thanks for the pointer, I am now running again.

Barry



On Sat, 2005-01-01 at 16:21 -0800, Ned Konz wrote:
> On Saturday 01 January 2005 8:03 am, Barry Bridgens wrote:
> > I am getting this when trying to open a SqueakMap Package Loader in a
> > fresh 3.7-5989-Full image. I am sure that I could do this before, has
> > anything changed on the SqueakMap side?
> 
> This looks like the 2Gb problem. I was getting that when I used
> 
>  -mmap 512M
> 
> but not when I used the default (which on my system would be 1024M).
> 
> What command-line arguments are you using?
> 
> How much virtual memory is available?
>