What platform are you on? You can raise the RAM limits the VM allows on a mac by editing the Info.plist file in the vm bundle. By default the limit is set to: <key>SqueakMaxHeapSize</key> <integer>536870912</integer> So maybe if you're on a Mac you can move that up to a larger number and the GC will complete. Hope this helps Paul Peter Uhnák wrote
In moment of my utter brilliance I managed to save image without noticing that I have infinite loop running... So it obviously crashed and launching is quite problematic. I managed to recompile infringing method from a startup script, since it seems strangly that it has higher priority, however right after that garbage collection kicks in and due to (probably) massive accumulated stack it dies again...(it is a nice 875M image -_-) ~~~~~~~~~ Smalltalk stack dump: 0xff916d80 I SmalltalkImage>lowSpaceWatcher 0xb7674470: a(n) SmalltalkImage 0xf2ae8a2c s [] in SmalltalkImage>installLowSpaceWatcher 0xf2ab50e0 s [] in BlockClosure>newProcess
stack page bytes 4096 available headroom 3300 minimum unused headroom 3524
(out of memory) ~~~~~~~~~
Is there some magic remedy for this?
It seems that there is a small window between starting the image and it crashing where I can do some little things; I managed to file out the most critical package like this, however I don't know where else I was making changes (day-ish of work)...
The loop itself is announcement-based, so maybe that's why there is some room for experimenting...
Thanks, Peter
-- View this message in context: http://forum.world.st/breaking-infinite-loop-from-saved-image-tp4832548p4832... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.