Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Hi Ronie, On Tue, Mar 14, 2017 at 5:08 PM, Ronie Salgado wrote: > Hi Alex, > > I gave the following script: > > Smalltalk compiler evaluate: ' >> | surface | >> surface := AthensCairoSurface extent: 640@480. >> surface drawDuring: [ :canvas | >> surface clear: Color

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Hi Alex, I gave the following script: Smalltalk compiler evaluate: ' > | surface | > surface := AthensCairoSurface extent: 640@480. > surface drawDuring: [ :canvas | > surface clear: Color blue. > ]. > > surface asForm asMorph openInWindow > ' > Notice that I am wrapping the script in a

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Hi Ronie, Below you said: > The problem with asForm, is that the form returned can be used after the > cairo surface which holds the pixels is garbage collected. I cannot reproduce this case. You gave a script: > surface := AthensCairoSurface extent: 640@480. > surface drawDuring: [ :canvas |

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

First option is clean but there is no way to get the surface back to do further things. Second keeps the surface around and this is pretty useful and the class name implies there is something about Athens in there. Now can't we have it both ways? By default it is the second option but when we,

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Hi, How about changing AthensCairoSurface >> asForm into the following definition?: asForm "create a form and copy an image data there" | form | self checkSession. self flush. form := Form extent: (self width@self height) depth: 32. form unhibernate. LibC memCopy:

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

would be possible to have one of your crashing images? so I can test… because one of my problems is that I’m not able to reproduce the problem when I try, and is hard to fix blindly... Esteban > On 21 Dec 2016, at 08:09, Alexandre Bergel wrote: > > I had plenty of

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Hi Nicolai, Thanks for the explanation! Peter said that his fix works for Windows. Why would this fix only work for Windows? And what can we do for other platforms? Cheers, Doru > On Dec 21, 2016, at 8:48 AM, Nicolai Hess wrote: > > > > Am 21.12.2016 8:10 vorm.

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Am 21.12.2016 8:10 vorm. schrieb "Alexandre Bergel" : I had plenty of elements in my Roassal visualization, and on some point it just crashed. I have the impression that having many elements and / or animations (as in the case of Johan Fabry) triggers the crash. One

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Just to make clear, I am using the latest VM on Mac OS X, El capitan, latest Pharo. The crashes I experienced are not new. My original email was not a complain (even if it may be perceived as one), but more to trigger a discussion. Peter did an excellent report of the current state of this

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

I had plenty of elements in my Roassal visualization, and on some point it just crashed. I have the impression that having many elements and / or animations (as in the case of Johan Fabry) triggers the crash. Alexandre > On Dec 20, 2016, at 9:12 AM, Stephane Ducasse

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

FreeType crashes are different, and I do experience them ocassionally (unlike Roassal ones), but they should be discussed in another thread. Peter On Tue, Dec 20, 2016 at 12:46:30PM +0100, p...@highoctane.be wrote: > Clement told me that a number of these crashes have been solved eons ago in >

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Clement told me that a number of these crashes have been solved eons ago in the opensmalltalkvm and that we are lagging behind with the integration of these things. I am a clueless n00b on what this was about, so, what is the exact status? I possibly face the same kind of issues in other areas

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

So what was your crash problem? On Tue, Dec 20, 2016 at 8:43 AM, Alexandre Bergel wrote: > > so did it work? > > Is there something that we should do? > > I had no problem, but as Henrik and Peter said, the problem is likely to > be more complex > > Alexandre > > > > >

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

> so did it work? > Is there something that we should do? I had no problem, but as Henrik and Peter said, the problem is likely to be more complex Alexandre > > On Fri, Dec 16, 2016 at 5:06 PM, Alexandre Bergel > wrote: > Okay, trying… > > Alexandre > > > > On

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Wow! Wonderful experience report! Alexandre > On Dec 19, 2016, at 2:03 PM, Peter Uhnak wrote: > > On Mon, Dec 19, 2016 at 08:12:29AM +0800, Ben Coman wrote: >> Can yo point to where you added you workaround? > > The fix is a single line, because I hate myself. > >

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

. canvas form inspect. Best regards, Henrik From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Stephane Ducasse Sent: Monday, December 19, 2016 10:09 PM To: Pharo Development List <pharo-dev@lists.pharo.org> Subject: Re: [Pharo-dev] [Moose-dev] Too frequent crashes :

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

so did it work? Is there something that we should do? On Fri, Dec 16, 2016 at 5:06 PM, Alexandre Bergel wrote: > Okay, trying… > > Alexandre > > > > On Dec 16, 2016, at 4:40 PM, Aliaksei Syrel > wrote: > > > > According to crash.dmp

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Okay, trying… Alexandre > On Dec 16, 2016, at 4:40 PM, Aliaksei Syrel wrote: > > According to crash.dmp TRMorph>drawOn: draws an image using > FormCanvas>>#image:at:sourceRect:rule: at a coordinate represented by a > Float point. > Try to round it to integer point. >

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

According to crash.dmp TRMorph>drawOn: draws an image using FormCanvas>>#image:at:sourceRect:rule: at a coordinate represented by a Float point. Try to round it to integer point. Cheers, Alex On 16 December 2016 at 16:34, Alexandre Bergel wrote: > Hi! > > Vincent and