Re: [Pharo-users] Crash in Athens

2017-03-05 Thread Igor Stasenko
On 5 March 2017 at 11:03, Esteban Lorenzano wrote: > > On 5 Mar 2017, at 05:00, Alexander Samoylovich > wrote: > > Hi Ronie, Esteban. > > Ronie's suggestion in the form Esteban presented it helped. > After implementing the fix I failed to crash my

Re: [Pharo-users] Crash in Athens

2017-03-05 Thread Esteban Lorenzano
> On 5 Mar 2017, at 05:00, Alexander Samoylovich wrote: > > Hi Ronie, Esteban. > > Ronie's suggestion in the form Esteban presented it helped. > After implementing the fix I failed to crash my application any more. > > Will anybody be so kind to explain me what

Re: [Pharo-users] Crash in Athens

2017-03-04 Thread Alexander Samoylovich
Hi Ronie, Esteban. Ronie's suggestion in the form Esteban presented it helped. After implementing the fix I failed to crash my application any more. Will anybody be so kind to explain me what actually happens and why the fix works? It looks so innocent. As far as I understand we do one

Re: [Pharo-users] Crash in Athens

2017-03-01 Thread Igor Stasenko
On 1 March 2017 at 05:42, Alexander Samoylovich wrote: > Thanks everybody for the explanation. > > I tried to apply Igor's suggestion. I allocate an offscreen surface 1 row > larger than needed > and when converting discard one row. > > The code looks more stable now. The

Re: [Pharo-users] Crash in Athens

2017-03-01 Thread Esteban Lorenzano
> On 1 Mar 2017, at 04:42, Alexander Samoylovich wrote: > > Thanks everybody for the explanation. > > I tried to apply Igor's suggestion. I allocate an offscreen surface 1 row > larger than needed > and when converting discard one row. > > The code looks more stable

Re: [Pharo-users] Crash in Athens

2017-02-28 Thread Alexander Samoylovich
Thanks everybody for the explanation. I tried to apply Igor's suggestion. I allocate an offscreen surface 1 row larger than needed and when converting discard one row. The code looks more stable now. The test was up for about 30 minutes before crashing instead of 1 minute before the fix. Is it

Re: [Pharo-users] Crash in Athens

2017-02-27 Thread Stephane Ducasse
Tx igor I added https://pharo.fogbugz.com/f/cases/19764/Improve-comment-of-AthensCairoSurfaceForm On Mon, Feb 27, 2017 at 7:35 PM, Igor Stasenko wrote: > and i was dealing with it by adding 1 extra line to cairo surface, > but reporting 1 less to Form. Like so, bitblt still

Re: [Pharo-users] Crash in Athens

2017-02-27 Thread Igor Stasenko
and i was dealing with it by adding 1 extra line to cairo surface, but reporting 1 less to Form. Like so, bitblt still reads past the allowed size, but it is safe, because there are unused bit(s). On 27 February 2017 at 20:31, Igor Stasenko wrote: > > > On 27 February 2017

Re: [Pharo-users] Crash in Athens

2017-02-27 Thread Igor Stasenko
On 27 February 2017 at 12:29, Esteban Lorenzano wrote: > Hi, > > the problem wit Ronie’s fix is that (as he says) you are copying another > time the surface, before passing it to the VM (who makes yet-another-copy) > so this is not optimal… and you can see it when running

Re: [Pharo-users] Crash in Athens

2017-02-27 Thread Esteban Lorenzano
Hi, the problem wit Ronie’s fix is that (as he says) you are copying another time the surface, before passing it to the VM (who makes yet-another-copy) so this is not optimal… and you can see it when running the Tiger demo: there are a lot of pauses. So I would prefer the other approach he

Re: [Pharo-users] Crash in Athens

2017-02-24 Thread stepharong
Hi alex can you try the fix of ronie and let us know if it makes roassal more stable? Stef Dear Alexander, Sine the new FFI of Pharo, using Athens has become unreliable. This is a pity, but fixing this is not trivial at all (we have been trying for years). What exactly are you doing

Re: [Pharo-users] Crash in Athens

2017-02-23 Thread stepharong
Hi alexander Thanks for reporting to us your findings. Can you report on which - os - version os - which pharo vm (there is a system report option) - which image Stef Hello. I can reproduce the bug "semi-automatically". The tree classes I use to crash are attached. Run

Re: [Pharo-users] Crash in Athens

2017-02-22 Thread Alexander Samoylovich
Hello. I can reproduce the bug "semi-automatically". The tree classes I use to crash are attached. Run AthensFlyingStickMorph new openInWorld and wait. Sometimes it crashes immediately. Sometimes I have to wait a couple of minutes. If I done not resize the crash never or almost never happens.

Re: [Pharo-users] Crash in Athens

2017-02-22 Thread Ronie Salgado
Hello, http://forum.world.st/Too-frequent-crashes-td4927143i20.html#a4934027 Try changing AthensCairoSurface >> asForm into the following method: asForm "create a form and copy an image data there" | form | self checkSession. self flush. form := Form extent: (self

Re: [Pharo-users] Crash in Athens

2017-02-22 Thread Alexandre Bergel
Dear Alexander, Sine the new FFI of Pharo, using Athens has become unreliable. This is a pity, but fixing this is not trivial at all (we have been trying for years). What exactly are you doing with Athens? Alexandre > On Feb 22, 2017, at 12:55 AM, Alexander Samoylovich

Re: [Pharo-users] Crash in Athens

2017-02-21 Thread Ben Coman
On Wed, Feb 22, 2017 at 11:55 AM, Alexander Samoylovich wrote: > Hello > > I am writing graphic demo programs using Athens on Mac Sierra. > Time by time Pharo VM crashes. Programs not using Athens work reliably. > I believe the behavior is reproducible. > How should I

[Pharo-users] Crash in Athens

2017-02-21 Thread Alexander Samoylovich
Hello I am writing graphic demo programs using Athens on Mac Sierra. Time by time Pharo VM crashes. Programs not using Athens work reliably. I believe the behavior is reproducible. How should I report a bug? Alex