Re: [Pharo-users] Saving image sometimes corrupts it

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] Saving image sometimes corrupts it

Nicolai Hess


2015-07-14 11:38 GMT+02:00 Jan Blizničenko <[hidden email]>:
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+%E2%80%93+crashing.zip
and here is the same image saved again which runs fine: http://www.mediafire.com/download/86djppsn1ds3c0o/Pharo+5.0+%28beta%29-50170-ok.zip
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

FT2Handle needs to cleanUp on exit, not on startup

and


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


Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] Saving image sometimes corrupts it

Jan Blizničenko
Nicolai Hess <nicolaihess@...> writes:

>
>
>
> 2015-07-14 11:38 GMT+02:00 Jan Blizničenko <bliznjan-
s88eNO7/[hidden email]>: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+%E2%80%93+crashing.zip
> and here is the same image saved again which runs fine:
http://www.mediafire.com/download/86djppsn1ds3c0o/Pharo+5.0+%28beta%29-
50170-ok.zip
> 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/shutdown15633

> FT2Handle needs to cleanUp on exit, not on startup
>
>
> and
>
> 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
>
>

Yes, it looks that's the problem, I am sorry I missed it
before. Thank you.

Jan
 
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] Saving image sometimes corrupts it

philippeback
In reply to this post by Nicolai Hess
I have had some Windows|Linux image transfers fail because I was using some .so libraries on Linux and the image wasn't agreeing to work properly/crashed on Windows (due to those missing I guess).

Not having seen those since I am sticking to CentOS now.

Phil

On Tue, Jul 14, 2015 at 11:47 AM, Nicolai Hess <[hidden email]> wrote:


2015-07-14 11:38 GMT+02:00 Jan Blizničenko <[hidden email]>:
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+%E2%80%93+crashing.zip
and here is the same image saved again which runs fine: http://www.mediafire.com/download/86djppsn1ds3c0o/Pharo+5.0+%28beta%29-50170-ok.zip
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

FT2Handle needs to cleanUp on exit, not on startup

and


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