I got this error maybe once or twice maybe a year ago on linux, but I had a lot of windows opened (like 20 or 30), and when I got back to big screen it was ok again. Peter On Thu, Mar 17, 2016 at 8:51 PM, stepharo <stepharo@free.fr> wrote:
Jan
I'm always switching monitor and I did not get it. Are you on mac? The bug I got is when I change manually the display extent: There it crashes from time to time.
Stef
Le 17/3/16 18:14, Jan Kurš a écrit :
Hi,
Looks like I know this bug. The problem is when you save the image on a big screen (with external monitor) and try to open it on a small one (without the external monitor). The same behaviour (for me) as in this case:
<https://pharo.fogbugz.com/f/cases/15944/Image-crash-on-Pharo-due-to-fonts-on...> https://pharo.fogbugz.com/f/cases/15944/Image-crash-on-Pharo-due-to-fonts-on...
Cheers, Jan
On Tue, Mar 15, 2016 at 10:48 PM Damien Pollet <damien.pollet@gmail.com> wrote:
Any idea what version of the image should be relatively stable ?
On 15 March 2016 at 07:31, Max Leske <maxleske@gmail.com> wrote:
I should have looked at the attachment⦠What youâre seeing is a problem with UFFI, Esteban is trying to hunt down the cause. For some reason the font loading mechanism uses an FFI call that doesnât always do what itâs supposed to. Usually this will lead to a playground or browser displaying a red âsquare for deathâ after boot but Iâve also seen segfaults myself.
This (very likely) has nothing to do with image size, as I suggested earlier.
Unfortunately, I donât think there is a fix at the moment other than trying save a new copy of the image.
Cheers, Max
On 15 Mar 2016, at 01:54, Ben Coman <btc@openInWorld.com> <btc@openInWorld.com> wrote:
On Tue, Mar 15, 2016 at 1:25 AM, Jan Kurš <kurs@inf.unibe.ch> wrote:
Hi,
I am trying to open an image I saved a few days ago and I am getting this message (the whole log is attached):
stack page bytes 4096 available headroom 2788 minimum unused headroom 3020
(Segmentation fault)
Anyone experiencing something similar? I am running the latest pharo5 VM on Linux.
Cheers, Jan
Something similar happened to me for the first time last night, about three times in quick succession. Seemed to be when I started an Image from a shell and later killed it with control-C. Incidentally, these was with a recent Tracker image only an hour old for me, which had locked while I was doing risky changes to DelayScheduler, but I was surprised that it affected the Image on disk. I was doing temporary checkpoint saves just prior to Accepting risky code changes. Then upon restart I got the error. But I could not reliably reproduce the problem.
Certainly it was not a large Image.
VM: http://files.pharo.org/vm/pharo-spur32/linux/463.zip Image: https://ci.inria.fr/pharo/view/5.0-Analysis/job/Pharo-5.0-Issue-Tracker-Imag... Platform: Debian 8 Jessie 32-bit
cheers -ben
-- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet