Sorry, but the details matter a lot: Which image version, vm version, os ?
You can use the System Reporter tool for this. Image ----- /Users/sven/Develop/Smalltalk/Pharo-Bootstrap.image Pharo3.0 Latest update: #30750 Unnamed Virtual Machine --------------- /Users/sven/Develop/Smalltalk/Pharo3.0.app/Contents/MacOS/Pharo NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <[email protected]> Jenkins build #14535 Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< VMMaker versionString git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <[email protected]> Jenkins build #14535 NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 Does this happen with a virgin image ? Probably not, what code did you load ? Sven On 12 Feb 2014, at 14:37, Holger Hans Peter Freyther <[email protected]> wrote: > On Mon, Oct 07, 2013 at 11:19:48AM +0200, Holger Hans Peter Freyther wrote: > > Hi, > >> I saved an image and today I wanted to resume it. Everything comes up, >> for a second I can interact with it (e.g. move a window) but then the >> pharo VM goes to 100% CPU usage. I let it run while writing this email >> and it eventually aborted: > > I keep on experiencing the issue on image resume. It appears that my > timer process runs before the startUp list of DateAndTime has been > executed and then anything using DateAndTime will get stuck. > > Is this a known issue of Pharo2.0? Couldn't >>#snapshot:andQuit: of > SmalltalkImage suspend all other processes and only resume them once > the startUp list has been executed? > > Any ideas how to debug that? I have started to explore bits of the > system using the commandline feature of Pharo. > > > Backtrace of the active process that appears to take all the CPU > > All Smalltalk process stacks (active first): > Process 0x7890adb8 priority 70 > 0xbf9a5e60 M DateAndTime>normalize:ticks:base: 0x799930dc: a(n) DateAndTime > 0xbf9a5e84 M DateAndTime>ticks:offset: 0x799930dc: a(n) DateAndTime > 0xbf9a5ea8 M DateAndTime>offset: 0x79992fe4: a(n) DateAndTime > 0xbf9a5ec4 M DateAndTime>asLocal 0x79992fe4: a(n) DateAndTime > 0xbf9a5ee4 M DateAndTime>- 0x7890ac98: a(n) DateAndTime > 0xbf9a5f00 M DateAndTime>asSeconds 0x7890ac98: a(n) DateAndTime > 0xbf9a2df0 M DateAndTime>< 0x7890ac98: a(n) DateAndTime > 0xbf9a2e0c M DateAndTime(Magnitude)>> 0x79992cb0: a(n) DateAndTime > 0xbf9a2e2c M TimerScheduler>fireTimers: 0x77fdb260: a(n) TimerScheduler > 0xbf9a2e54 I [] in TimerScheduler>runTimers 0x77fdb260: a(n) TimerScheduler > 0xbf9a2e70 M BlockClosure>on:do: 0x7890acac: a(n) BlockClosure > 0xbf9a2e94 M [] in Dispatcher>dispatch 0x77fdb018: a(n) Dispatcher > 0xbf9a2eb4 M BlockClosure>ensure: 0x7890ae38: a(n) BlockClosure > 0xbf9a2ee0 I [] in Dispatcher>dispatch 0x77fdb018: a(n) Dispatcher > 0xbf9a2f00 I [] in BlockClosure>newProcess 0x7890acd4: a(n) BlockClosure > > same image some seconds later > > All Smalltalk process stacks (active first): > Process 0x7890adb8 priority 70 > 0xbf9a2d78 M Fraction>reduced 0x7ac6cb4c: a(n) Fraction > 0xbf9a2d90 M SmallInteger>/ 0x1903d=51230 > 0xbf9a2dac M DateAndTime>julianDayOffset 0x7ac6ca1c: a(n) DateAndTime > 0xbf9a2dc8 M DateAndTime>julianDayNumber 0x7ac6ca1c: a(n) DateAndTime > 0xbf9a2df0 M DateAndTime>< 0x7890ac98: a(n) DateAndTime > 0xbf9a2e0c M DateAndTime(Magnitude)>> 0x7ac6ca1c: a(n) DateAndTime > 0xbf9a2e2c M TimerScheduler>fireTimers: 0x77fdb260: a(n) TimerScheduler > 0xbf9a2e54 I [] in TimerScheduler>runTimers 0x77fdb260: a(n) TimerScheduler > 0xbf9a2e70 M BlockClosure>on:do: 0x7890acac: a(n) BlockClosure > 0xbf9a2e94 M [] in Dispatcher>dispatch 0x77fdb018: a(n) Dispatcher > 0xbf9a2eb4 M BlockClosure>ensure: 0x7890ae38: a(n) BlockClosure > 0xbf9a2ee0 I [] in Dispatcher>dispatch 0x77fdb018: a(n) Dispatcher > 0xbf9a2f00 I [] in BlockClosure>newProcess 0x7890acd4: a(n) BlockClosure > >
