Using SqueakMap on a fresh 3.8 Image for the first time -> CPU
100% for an hour
Günther Schmidt
gue.schmidt at web.de
Sat Jun 3 21:16:08 UTC 2006
Dear Milan,
Milan Zimmermann schrieb:
> Günter,
>
> Before going to next step, could you send here the message the the system gave
> you at the end when it said it failed? It may be interesting for someone to
> help debugging it. Also please attach file named "SqueakDebug.log" from the
> directory where your image is located.
>
I will, thanks for the offer, but it'll be an hour + or so, during which
my machine will pretty much be frozen up.
> As to trying to fix your problem quickly (and I am not sure it will help):
>
> 1) This may not be the "correct approach", but try it: in the directory where
> your image runs from, there is a directory named "sm" - remove it and try SM
> again. This may be too radical, but should work.
>
> 2) There is another way I now cannot find on the list on first try .. a
> command from workspace.
>
> Milan
>
>
> On 2006 June 3 16:03, Günther Schmidt wrote:
>> Hi all,
>>
>> I'm using a clean 3.8 image with the current VM from Squeak.org on XP.
>>
>> Whenever I want to load SMPackageLoader for the first time, the system
>> tells me I need to update to a newer client version of SM.
>>
>> Fine sofar, I'll just do that then. (Klicking OK)
>>
>> Next thing the system tells me it's snapshotting methods, and the CPU
>> usage is at 100% for the next 1 1/2 hours.
>>
>> Every time.
>>
>> Does anybody know, what's causing this, and how to prevent it?
>>
>> Oh and sometimes I make it through the 1 1/2 hours just to have the
>> system let me know that it failed.
>>
>> Please help!
>>
>> Günther
>
>
More information about the Squeak-dev
mailing list
|