> On 30 Jul 2016, at 14:19, Holger Freyther wrote:
>
>
>> On 30 Jul 2016, at 13:14, Esteban Lorenzano wrote:
>>
>> hi Holger,
>>
>> do you have a reproducible way for this error? it happens always?
>
> three times in a row, with the latest image.
Esteban,
The segfault is in the same method that I reported yesterday (with a
very reproducible test case)[1] ... also part of big 18706[2]
[1]
http://forum.world.st/segfault-fresh-Pharo5-0-download-w-pharo-VM-version-5-0-1-Wed-May-4-11-54-28-CEST-2016-gcc-4-6-3-Pro-tt4908706.html
[2]
> On 30 Jul 2016, at 13:14, Esteban Lorenzano wrote:
>
> hi Holger,
>
> do you have a reproducible way for this error? it happens always?
three times in a row, with the latest image. 50759 seems to be fine or I was
lucky. The difference is small/odd. Let me try the
> On 30 Jul 2016, at 13:14, Esteban Lorenzano wrote:
>
> hi Holger,
>
> do you have a reproducible way for this error? it happens always?
I have the impression that most derived 5.0 builds fail now, for example:
hi Holger,
do you have a reproducible way for this error? it happens always?
cheers,
Esteban
> On 30 Jul 2016, at 08:45, Holger Freyther wrote:
>
>
>> On 17 Mar 2016, at 22:16, Peter Uhnák wrote:
>
> Hi!
>
>
>> I got this error maybe once or twice
> On 17 Mar 2016, at 22:16, Peter Uhnák wrote:
Hi!
> 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.
I am now seeing this with a Pharo50 build on a
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:
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 wrote:
> Jan
>
> I'm always switching monitor and I did not
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
Any idea what version of the image should be relatively stable ?
On 15 March 2016 at 07:31, Max Leske 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
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
On Tue, Mar 15, 2016 at 1:25 AM, Jan Kurš 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)
>
How large is your image? There’s a bug in the VM where it can’t open large
images.
> On 14 Mar 2016, at 18:25, Jan Kurš 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
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.
14 matches
Mail list logo