VM crash with image 3.9

Damien Cassou damien.cassou at gmail.com
Sun May 27 09:51:41 UTC 2007


2007/5/27, John M McIntosh <johnmci at smalltalkconsulting.com>:
> The clue here is the magic number
>
> -2145977416 >new:
> -2145977508 NSStringWriter>nextPutAll:
> -2145977600 [] in NSBenchmarks>benchStringNextPutAllString
> -2145977692 Integer>timesRepeat:
> 2030103240 [] in NSBenchmarks>benchStringNextPutAllString
>
> in front of the stack trace which is the memory address for the
> stack. It's gone negative since you've gone over the 2GB boundary.
> However most VMs out there are NOT safe to run with addresses > 2GB.
> They die, as you see.


If I understand correctly, my algorithm uses far too much memory and
this memory is never GCed.


> There has been work lately by David T Lewis to address this issue but
> I don't think it has been compiled into any of the official VMs yet.
>
> If this is unix try fiddling with the memory parm value to see if you
> can load the VM lower down in virtual memory.

What is this value? How do I change it?

-- 
Damien Cassou



More information about the Squeak-dev mailing list