[Vm-dev] Spur corrupts large images when saving

Tudor Girba tudor at tudorgirba.com
Fri Apr 22 07:30:22 UTC 2016


Thanks for reporting. Indeed, I just encountered a similar situation with a 900Mb image.

Cheers,
Doru


> On Apr 22, 2016, at 9:17 AM, Yuriy Tymchuk <yuriy.tymchuk at me.com> wrote:
> 
> The script can be still used to reproduce the issue with the latest vm
> 
>> On 07 Mar 2016, at 22:32, Yuriy Tymchuk <yuriy.tymchuk at 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+vmLatest | 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
> 

--
www.tudorgirba.com
www.feenk.com

"We are all great at making mistakes."










More information about the Vm-dev mailing list