A few months ago, we lost weeks of user updates due to image persistence saving itself as an unlaunchable image (> 1GB interpreter). All the latest code for SqueakSource is ready and available at http://source.squeak.org/ss. This is the codebase that has been supporting source.squeak.org for several months now. It's stable.
Squeaksource is important. Is there any reason not to update the image and code ASAP?
On Fri, Mar 24, 2017 at 1:44 PM, Levente Uzonyi leves@caesar.elte.hu wrote:
Okay, I downloaded the image and started up on my machine. It greeted me with 2 errors. Both were related to not being able to start up the web server. Does this image save itself periodially? If so, it was saved when it had these debuggers open, basically killing itself.
Levente
On Fri, 24 Mar 2017, Levente Uzonyi wrote:
Hi All,
as you may know, squeaksource.com is down. I had a look and found that
- the image had fallen into a GC cycle consuming 100% cpu and about 500 MB
o memory
- restarting the image didn't help with that
- I added the -mmap 1024m parameter to its arguments, and it stopped the
CPU grinding, and the memory usage has fallen below 500 MB since then. This also means that the VM's default memory limit is actually 500MB contrary to the 1GB stated by the VM.
- but, the image is still not able to start up properly. it's probably
stuck on something simple, but due to the lack of VNC, I just couldn't check what was wrong
Levente