Helge,

There should either be a SqueakDebug.log and/or a crash.dmp file telling us
a little more about what the problem is.

  - Andreas

> -----Original Message-----
> From: Helge Horch [mailto:Helge.Horch at munich.netsurf.de]
> Sent: Tuesday, May 29, 2001 1:34 PM
> To: squeak at cs.uiuc.edu
> Cc: recipient list not shown
> Subject: 3.1a WinVM trouble with huge image
> 
> 
> Folks,
> 
> I have managed to produce a relatively large image snapshot 
> (426 MB) with a 
> half-completed longish computation, and to my surprise I 
> cannot reopen it 
> with any of the recent 3.1a Windows VMs 3.1a3, 3.1a4, or 3.1a6 (on 
> NT4SP4).  I don't get an emergency evaluator nor a crash.dmp nor a 
> SqueakDebug.log though, so I can only describe symptoms:  The 
> VM grabs 440M 
> of memory, spends 15 seconds before it opens the Squeak 
> window (blank), 
> flashes a flurry of messages in the subwindow at the bottom shortly 
> thereafter, and vanishes in a small puff of smoke.
> 
> The 3.0bld2 VM, when given -memory: 600, happily opens said 
> image.  (Well, 
> the machine thrashes for a while, but at least the data is still 
> accessible.  Phew.)
> 
> I should sprinkle fprintf's in the code, but have to fetch 
> the new "tool 
> junta" and system-specific sources first.  In the meantime, I wonder 
> whether anyone has experienced this before?  Any hints as to 
> where would be 
> a good place to look first?
> 
> Cheers,
> Helge
>