sweep failed to find exact end of memory

Andreas Raab andreas.raab at gmx.de
Tue Sep 12 16:45:35 UTC 2006


I think you're seeing the old problem of signed vs. unsigned ints when 
accessing memory locations (the negative numbers seem to indicate that 
much). Try a later VM (3.9-7 is the latest according to SqueakVM.org) - 
IIRC, then this problem got fixed in later versions.

Cheers,
   - Andreas

Avi Bryant wrote:
> I'm seeing this on a unix 3.7-7 VM running on Linux: if I start it with 
> an image larger than exactly 400MB, it fails immediately with this stack 
> trace:
> 
> sweep failed to find exact end of memory
> 
> -1731071872 SystemDictionary>garbageCollect
> -1731071964 WeakArray class>isFinalizationSupported
> -1731072084 WeakArray class>restartFinalizationProcess
> -1731072176 WeakArray class>startUp:
> ...
> 
> The same image opens fine on my MacBook with whichever VM.
> 
> Anyone have any idea what's going on?
> 
> Avi
> 
> 




More information about the Squeak-dev mailing list