[Pharo-dev] 100% CPU usage on image resume

Camillo Bruni camillobruni at gmail.com
Mon Oct 7 05:32:13 EDT 2013


which pharo version?
which vm version?
which OS?

On 2013-10-07, at 11:19, Holger Hans Peter Freyther <holger at freyther.de> 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:
> 
> C stack backtrace:
> ./pharo[0x80a0c0c]
> ./pharo(error+0x19)[0x80a0f69]
> ./pharo[0x80785d3]
> ./pharo[0x80786e1]
> ./pharo[0x8078f10]
> ./pharo[0x8090d97]
> ./pharo(ceStackOverflow+0x6a)[0x80946ea]
> [0x76ef122e]
> ./pharo(interpret+0x7a6)[0x8094f36]
> ./pharo(main+0x2b3)[0x80a18b3]
> /lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xf5)[0xb74bb8c5]
> 
> 
> Smalltalk stack dump:
> 0xbfd5c610 M SmallInteger(Number)>negative     0x3841=7200
> 0xbfd5c630 M SmallInteger(Integer)>*     0x3841=7200
> 0xbfd5c64c M SmallInteger>*     0x3841=7200
> 0xbfd5c668 M Duration>asNanoSeconds 0x790ddef4: a(n) Duration
> 0xbfd5c684 M Duration>= 0x7fe004a0: a(n) Duration
> 0xbfd5c6a0 M DateAndTime>asLocal 0x7fe00488: a(n) DateAndTime
> 0xbfd5c6c0 M DateAndTime>- 0x7fe0040c: a(n) DateAndTime
> 0xbfd5c6dc M DateAndTime>asSeconds 0x7fe0040c: a(n) DateAndTime
> 0xbfd5c700 M DateAndTime>< 0x78d2a5f8: a(n) DateAndTime
> 0xbfd5c71c M DateAndTime(Magnitude)>> 0x7fe0040c: a(n) DateAndTime
> 0xbfd5c73c M TimerScheduler>fireTimers: 0x77ef49ac: a(n) TimerScheduler
> 0xbfd5c764 I [] in TimerScheduler>runTimers 0x77ef49ac: a(n) TimerScheduler
> 0xbfd5c780 M BlockClosure>on:do: 0x78d2a60c: a(n) BlockClosure
> 0xbfd5c7a4 M [] in Dispatcher>dispatch 0x77ef4764: a(n) Dispatcher
> 0xbfd5c7c4 M BlockClosure>ensure: 0x78d2a798: a(n) BlockClosure
> 0xbfd5c7f0 I [] in Dispatcher>dispatch 0x77ef4764: a(n) Dispatcher
> 0xbfd5c810 I [] in BlockClosure>newProcess 0x78d2a634: a(n) BlockClosure
> 
> Most recent primitives
> 
> stack page bytes 4096 available headroom 3300 minimum unused headroom 3508
> 
> 	(last object overwritten)
> Aborted
> 
> 
> TimerScheduler/Dispatcher is code of mine but I wouldn't understand why this
> code is getting blocked and would eventually cause a stack overflow?
> 
> holger
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 447 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131007/6b8e5ffb/attachment.asc>


More information about the Pharo-dev mailing list