On 08 Mar 2016, at 16:30, Eliot Miranda <eliot.miranda@gmail.com> wrote:Yuriy, Steph,Yes, I’m using VMMaker.oscog-EstebanLorenzano.1676ignore my earlier response. You need to use a newer VM. The problem was fixed in VMMaker.oscog-eem.1679 so move to a newer VM.
_,,,^..^,,,_ (phone)Thank youOn 08 Mar 2016, at 06:08, Eliot Miranda <eliot.miranda@gmail.com> wrote:Hi Yuriy,what's the version info in that VM? I expect this is the same bug I fixed inCogVM binaries as per VMMaker.oscog-eem.1679/r3602...Fix start up of images containing >= 16 segments. The old code assumednumSegments < 16 and failed to grow the segment records, resulting in objectsin segments greater than 15 to not be swizzled, and a resulting crash.
_,,,^..^,,,_ (phone)Dear vm developers,I’ve encountered multiple times an issue when my images cannot be opened after saving (only on spur). I think that this happens when image is large, and the following script results in a corrupt image almost 100%:curl get.pharo.org/50+vm | bash./pharo Pharo.image --no-default-preferences eval --save \"Smalltalk globals at: #ReallyBigArray put: (ByteArray new: 1024*1024*1000). 'Done'"./pharo Pharo.image printVersionThe last line is there just to make image do something and for me it fails all the times. I hope that this can help to troubleshoot the issue with the vm.Also here are my system & hardware specs:System Version: OS X 10.11.3 (15D21)Model Identifier: MacBookPro11,5Processor Name: Intel Core i7Processor Speed: 2.8 GHzTotal Number of Cores: 4Memory: 16 GBCheers!Uko