On 08 Mar 2016, at 13:48, Esteban Lorenzano <estebanlm@gmail.com> wrote:

can you try with vmLatest, to check if Eliot change fix it?

Esteban

On 08 Mar 2016, at 11:43, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:

Yes, I’m using VMMaker.oscog-EstebanLorenzano.1676

Thank you

On 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 in

CogVM binaries as per VMMaker.oscog-eem.1679/r3602

 ...

Fix start up of images containing >= 16 segments.  The old code assumed

numSegments < 16 and failed to grow the segment records, resulting in objects

in segments greater than 15 to not be swizzled, and a resulting crash.

_,,,^..^,,,_ (phone)

On Mar 7, 2016, at 1:32 PM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:

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 printVersion

The 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,5

Processor Name: Intel Core i7

Processor Speed: 2.8 GHz

Total Number of Cores: 4

Memory: 16 GB

Cheers!

Uko