Of course, this seems like it. Sorry for missing that it is already known problem. Thank you Jan Nicolai Hess wrote

2015-07-14 11:38 GMT+02:00 Jan Blizničenko <

bliznjan@.cvut

>:

...

Hello

I come with another probably-only-mine-windows-related problem which I am unable to reproduce from a clean image. I use latest image 50170, latest (9th July 2015) Windows VM, Windows 7 64bit. So there is my vague description: When I load some project, modify it few times and save it, then SOMETIMES (seems random to me) when I try to open this saved image, it immediately crashes VM and does not even produce crash.dmp file (well, it creates it, but empty).

For example, I have such image... I save it, do not close it, try to open it, crash, save it again, try to open it, it runs, save it again, close, try to open it, crash. Without any change inside the image by my hand.

I tried doing something similar with clean image, but it never corrupted it.

I am unable to open such image even on my Linux machine. It at least generates output when segmentation fault happens: http://pastebin.com/KLry40Hu HDD I am saving it to does not show any signs of damage, everything else is working (and saving) just fine.

Here is such crashing image: http://www.mediafire.com/download/h5vhh7c40cl1w15/Pharo+5.0+%28beta%29-50170... and here is the same image saved again which runs fine: http://www.mediafire.com/download/86djppsn1ds3c0o/Pharo+5.0+%28beta%29-50170... However, when I open this "ok" image in linux, it causes segfault too.

I tried also opening working image in VM marked as stable (2015-09-24), then I saved it and there was the same problem.

This is probably all I know about it, although I am aware that it is not much, but I am in the dead end and this problem is really huge for me.

I think we still have an issue with freetype font face loading/caching on startup/shutdown

15633 <https://pharo.fogbugz.com/default.asp?15633>; FT2Handle needs to cleanUp on exit, not on startup

and

15944 <https://pharo.fogbugz.com/default.asp?15944>; Image crash on Pharo due to fonts on W7

...

I am on ESUG so if you are here too and think you might be able to help, I can show it to you personally.

Jan Blizničenko

-- View this message in context: http://forum.world.st/Saving-image-sometimes-corrupts-it-tp4837423p4837473.h... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

yes… I introduced that problem in Pharo 5. If you are using that version right now, it is my fault :) (but is Pharo 5 pre-alpha so we are ok with this instabilities for now… I will solve that after ESUG) cheers, Esteban

On 14 Jul 2015, at 14:51, Blondeau Vincent <vincent.blondeau@worldline.com> wrote:

Hello,

I have the same problem and it seems to be random. It is related to font cache.

I opened a bug related to it: https://pharo.fogbugz.com/f/cases/15944/Image-crash-on-Pharo-due-to-fonts-on...

I will raise the priority because it is very painful...

I am at ESUG too maybe we can discuss of it ;)

Vincent Blondeau ________________________________________ De : Pharo-users [pharo-users-bounces@lists.pharo.org] de la part de Jan Blizničenko [bliznjan@fit.cvut.cz] Date d'envoi : mardi 14 juillet 2015 11:38 À : pharo-users@lists.pharo.org Objet : [Pharo-users] Saving image sometimes corrupts it

Hello

I come with another probably-only-mine-windows-related problem which I am unable to reproduce from a clean image. I use latest image 50170, latest (9th July 2015) Windows VM, Windows 7 64bit. So there is my vague description: When I load some project, modify it few times and save it, then SOMETIMES (seems random to me) when I try to open this saved image, it immediately crashes VM and does not even produce crash.dmp file (well, it creates it, but empty).

For example, I have such image... I save it, do not close it, try to open it, crash, save it again, try to open it, it runs, save it again, close, try to open it, crash. Without any change inside the image by my hand.

I tried doing something similar with clean image, but it never corrupted it.

I am unable to open such image even on my Linux machine. It at least generates output when segmentation fault happens: http://pastebin.com/KLry40Hu HDD I am saving it to does not show any signs of damage, everything else is working (and saving) just fine.

Here is such crashing image: http://www.mediafire.com/download/h5vhh7c40cl1w15/Pharo+5.0+%28beta%29-50170... and here is the same image saved again which runs fine: http://www.mediafire.com/download/86djppsn1ds3c0o/Pharo+5.0+%28beta%29-50170... However, when I open this "ok" image in linux, it causes segfault too.

I tried also opening working image in VM marked as stable (2015-09-24), then I saved it and there was the same problem.

This is probably all I know about it, although I am aware that it is not much, but I am in the dead end and this problem is really huge for me.

I am on ESUG so if you are here too and think you might be able to help, I can show it to you personally.

Jan Blizničenko

Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.