December 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 86be50: 60332

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 86be50c96618776323023836fb3a36754b632cdd https://github.com/pharo-project/pharo-core/commit/86be50c96618776323023836… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-20 (Tue, 20 Dec 2016) Changed paths: M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version427_.st M Glamour-FastTable.package/GLMMorphicFTRenderer.class/instance/rendering/render_.st M Glamour-Morphic-Brick.package/GLMAlertBrick.class/instance/scripting/alert_.st M Glamour-Morphic-Brick.package/GLMBrickStructureTrait.class/instance/brick-structure-opening/openInBrickWindowLabeled_.st M Glamour-Morphic-Brick.package/GLMBrickStructureTrait.class/instance/brick-structure-opening/window.st M Glamour-Morphic-Brick.package/GLMPrivacyAgreementBrick.class/instance/preferences/sendUsageData.st M Glamour-Morphic-Widgets.package/GLMPrintPopper.class/instance/public/openFromRubric_withResult_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60331.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60332.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60331.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60332.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60332 19480 Update Glamour to version 4.27 https://pharo.fogbugz.com/f/cases/19480 http://files.pharo.org/image/60/60332.zip

Dec. 20, 2016

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

by Peter Uhnak

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, phil(a)highoctane.be wrote: > 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 and have been using > a Windows VM with StrikeFonts to have it stable. > > Phil > > > > > On Tue, Dec 20, 2016 at 9:12 AM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > > So what was your crash problem? > > > > > > On Tue, Dec 20, 2016 at 8:43 AM, Alexandre Bergel <alexandre.bergel(a)me.com > > > 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 > >> > >> > >> > > >> > On Fri, Dec 16, 2016 at 5:06 PM, Alexandre Bergel < > >> alexandre.bergel(a)me.com> wrote: > >> > Okay, tryingâ¦ > >> > > >> > Alexandre > >> > > >> > > >> > > On Dec 16, 2016, at 4:40 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> > >> 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. > >> > > > >> > > Cheers, > >> > > Alex > >> > > > >> > > On 16 December 2016 at 16:34, Alexandre Bergel < > >> alexandre.bergel(a)me.com> wrote: > >> > > Hi! > >> > > > >> > > Vincent and I are experiencing many crashes from GrafPort>copyBits. > >> It crashes every couple of minutes. > >> > > > >> > > I know that not much can be done so far. Stability is my biggest > >> concern with Pharo :-( > >> > > I use the latest VM. > >> > > > >> > > Cheers, > >> > > Alexandre > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > -- > >> > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >> > > Alexandre Bergel http://www.bergel.eu > >> > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >> > > > >> > > > >> > > > >> > > > >> > > _______________________________________________ > >> > > Moose-dev mailing list > >> > > Moose-dev(a)list.inf.unibe.ch > >> > > https://www.list.inf.unibe.ch/listinfo/moose-dev > >> > > > >> > > > >> > > >> > -- > >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >> > Alexandre Bergel http://www.bergel.eu > >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >> > > >> > > >> > > >> > > >> > > >> > >> -- > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >> Alexandre Bergel http://www.bergel.eu > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >> > >> > >> > >> > >> > >

Dec. 20, 2016

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

by phil＠highoctane.be

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 and have been using a Windows VM with StrikeFonts to have it stable. Phil On Tue, Dec 20, 2016 at 9:12 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > So what was your crash problem? > > > On Tue, Dec 20, 2016 at 8:43 AM, Alexandre Bergel <alexandre.bergel(a)me.com > > 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 >> >> >> > >> > On Fri, Dec 16, 2016 at 5:06 PM, Alexandre Bergel < >> alexandre.bergel(a)me.com> wrote: >> > Okay, tryingâ¦ >> > >> > Alexandre >> > >> > >> > > On Dec 16, 2016, at 4:40 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> >> 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. >> > > >> > > Cheers, >> > > Alex >> > > >> > > On 16 December 2016 at 16:34, Alexandre Bergel < >> alexandre.bergel(a)me.com> wrote: >> > > Hi! >> > > >> > > Vincent and I are experiencing many crashes from GrafPort>copyBits. >> It crashes every couple of minutes. >> > > >> > > I know that not much can be done so far. Stability is my biggest >> concern with Pharo :-( >> > > I use the latest VM. >> > > >> > > Cheers, >> > > Alexandre >> > > >> > > >> > > >> > > >> > > >> > > >> > > -- >> > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > > Alexandre Bergel http://www.bergel.eu >> > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > > >> > > >> > > >> > > >> > > _______________________________________________ >> > > Moose-dev mailing list >> > > Moose-dev(a)list.inf.unibe.ch >> > > https://www.list.inf.unibe.ch/listinfo/moose-dev >> > > >> > > >> > >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> > >> > >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >

Dec. 20, 2016

[pharo-project/pharo-core] 37f27a: 60331

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 37f27a06b50b8c74abc810d24e3cf9d838dbc413 https://github.com/pharo-project/pharo-core/commit/37f27a06b50b8c74abc810d2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-20 (Tue, 20 Dec 2016) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60330.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60331.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60330.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60331.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60331 18735 DNU on suggestions shortcut in GTDebugger https://pharo.fogbugz.com/f/cases/18735 http://files.pharo.org/image/60/60331.zip

Dec. 20, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60331 Home: https://github.com/pharo-project/pharo-core

Dec. 20, 2016

Re: [Pharo-dev] [Vm-dev] Problem with OSSubprocess / signals / heartbeat ?

by Guille Polito

Hi Holger, Just to add to the issue, when we talk about hanging, the VM thread is stopped in an FFI call, 0xffdfe1c0 I OSSUnixSubprocess>primitivePosixSpawn:command:fileActions:attributes:argPointer:envPointer: 0x9482438: a(n) OSSUnixSubprocess 0xffdfe200 I OSSUnixSubprocess>internalRun 0x9482438: a(n) OSSUnixSubprocess 0xffdfe220 I [] in OSSUnixSubprocess>run 0x9482438: a(n) OSSUnixSubprocess 0xffdf9fe0 M BlockClosure>ensure: 0x9482750: a(n) BlockClosure 0xffdfa004 I OSSUnixSubprocess>run 0x9482438: a(n) OSSUnixSubprocess 0xffdfa024 I OSSUnixSubprocess>runAndWaitOnExitDo: 0x9482438: a(n) OSSUnixSubprocess self ffiCall: #( int posix_spawnp (void* pidPointer, String commandString, void* fileActions, void * attributes, void* argPointer, void* envPointer) ) Now, here is an extract of the timestamped `strace -ftt` of the hanging process: [pid 24108] 10:28:09.044534 --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- [pid 24108] 10:28:09.044577 gettimeofday({1482226089, 44582}, NULL) = 0 [pid 24108] 10:28:09.044644 sigreturn() (mask []) = 120 [pid 24108] 10:28:09.044664 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf7500768) = ? ERESTARTNOINTR (To be restarted) [pid 24108] 10:28:09.050924 --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- [pid 24108] 10:28:09.050970 gettimeofday({1482226089, 50976}, NULL) = 0 [pid 24108] 10:28:09.050996 sigreturn() (mask []) = 120 [pid 24108] 10:28:09.051009 --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- [pid 24108] 10:28:09.051016 gettimeofday({1482226089, 51020}, NULL) = 0 [pid 24108] 10:28:09.051028 sigreturn() (mask []) = 120 [pid 24108] 10:28:09.051040 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf7500768) = ? ERESTARTNOINTR (To be restarted) [pid 24108] 10:28:09.066154 --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- [pid 24108] 10:28:09.066196 gettimeofday({1482226089, 66201}, NULL) = 0 [pid 24108] 10:28:09.066220 sigreturn() (mask []) = 120 [pid 24108] 10:28:09.066233 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf7500768) = ? ERESTARTNOINTR (To be restarted) [pid 24108] 10:28:09.072599 --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- [pid 24108] 10:28:09.072643 gettimeofday({1482226089, 72648}, NULL) = 0 [pid 24108] 10:28:09.072716 sigreturn() (mask []) = 120 [pid 24108] 10:28:09.072740 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf7500768) = ? ERESTARTNOINTR (To be restarted) [pid 24108] 10:28:09.079552 --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- [pid 24108] 10:28:09.079580 gettimeofday({1482226089, 79585}, NULL) = 0 [pid 24108] 10:28:09.079648 sigreturn() (mask []) = 120 [pid 24108] 10:28:09.079672 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf7500768) = ? ERESTARTNOINTR (To be restarted) [pid 24108] 10:28:09.089178 --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- [pid 24108] 10:28:09.089233 gettimeofday({1482226089, 89239}, NULL) = 0 [pid 24108] 10:28:09.089264 sigreturn() (mask []) = 120 [pid 24108] 10:28:09.089278 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf7500768) = ? ERESTARTNOINTR (To be restarted) [pid 24108] 10:28:09.101007 --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- [pid 24108] 10:28:09.101046 gettimeofday({1482226089, 101050}, NULL) = 0 [pid 24108] 10:28:09.101096 sigreturn() (mask []) = 120 [pid 24108] 10:28:09.101116 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf7500768) = ? ERESTARTNOINTR (To be restarted) [pid 24108] 10:28:09.107650 --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- [pid 24108] 10:28:09.107699 gettimeofday({1482226089, 107706}, NULL) = 0 [pid 24108] 10:28:09.107771 sigreturn() (mask []) = 120 [pid 24108] 10:28:09.107789 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf7500768) = ? ERESTARTNOINTR (To be restarted) [pid 24108] 10:28:09.116188 --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- [pid 24108] 10:28:09.116226 gettimeofday({1482226089, 116232}, NULL) = 0 [pid 24108] 10:28:09.116254 sigreturn() (mask []) = 120 [pid 24108] 10:28:09.116273 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf7500768) = ? ERESTARTNOINTR (To be restarted) [pid 24108] 10:28:09.129739 --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- The second trace in Mariano's email was a trace in the case of no FFI call. Just to compare both of them and their differences, but there is no hang in there. Although my knowledge arrives until here, I can help in providing any other traces or information. I asked Santa an OSSubprocess that won't hang :) Thanks, Guille -------- Original Message -------- > > >> On 19 Dec 2016, at 14:41, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> >> Hi guys, >> >> Guille Polito kept one of these images if someone can give us a hand. He also proposed the great idea of using `strace` to see what was going on. He (together with Pable Tesone) suspected that the heartbeat could be interrupting the `clone()` function which is (I think) called internally by the 'posix_spawn()' which is the one used by OSSubprocess. >> >> When these images are "hung" they found at a infinitive loop like this: > Okay, how many child processes do you have at that point? How many processes does the system have? > > >> [pid 17477] --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- >> [pid 17477] gettimeofday({1482152630, 593498}, NULL) = 0 >> [pid 17477] sigreturn() (mask []) = 120 >> [pid 17477] clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf7578768) = ? ERESTARTNOINTR (To be restarted) >> [pid 17477] --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- >> [pid 17477] gettimeofday({1482152630, 600126}, NULL) = 0 >> [pid 17477] sigreturn() (mask []) = 120 >> [pid 17477] clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf7578768) = ? ERESTARTNOINTR (To be restarted) > so above.. 7ms between the two gettimeofday calls? Nothing else? Set a breakpoint on clone/fork in gdb and look at the c-stack at this point? Could you strace with timestamps to see how much time is spent? Is the process suspicious in other ways? > > So yes.. sounds like clone doesn't complete.. the question is why? Is it out of resources? Is something in the VM blocking longer than the heartbeat, is the heartbeat more frequent than expected? > > >> As you can see, there is a SIGALARM involved. It also looks like the `gettimeofday` is used by the heartbeat ? Could it be that someone the heartbeat is interrupting the `clone()` ? >> >> Guille also showed me the `strace` output with a regular / working image: >> >> >> [pid 18647] --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- >> [pid 18647] gettimeofday({1482152829, 481014}, NULL) = 0 >> [pid 18647] sigreturn() (mask []) = -1 EINTR (Interrupted system call) >> [pid 18647] getitimer(ITIMER_REAL, {it_interval={0, 2000}, it_value={0, 1917}}) = 0 >> [pid 18647] recvmsg(3, 0xff7b0734, 0) = -1 EAGAIN (Resource temporarily unavailable) >> [pid 18647] select(4, [3], [], [3], {0, 1000}) = 0 (Timeout) >> [pid 18647] getitimer(ITIMER_REAL, {it_interval={0, 2000}, it_value={0, 797}}) = 0 >> [pid 18647] recvmsg(3, 0xff7b0734, 0) = -1 EAGAIN (Resource temporarily unavailable) >> [pid 18647] select(4, [3], [], [3], {0, 1000}) = ? ERESTARTNOHAND (To be restarted if no handler) >> [pid 18647] --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- >> >> >> Does anyone have any hint here? > Get timestamps in there. How long does it take to fail/end in this situation? > > holger > > > > >

Dec. 20, 2016

Re: [Pharo-dev] About Fraction and parentheses

by Sven Van Caekenberghe

Ah, OK, sorry about the misunderstanding. > On 20 Dec 2016, at 09:21, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > I think that I know that :) > And this is why I mentioned that if you print 1/3 it prints (1/3) so that we can continue typing + (2/3) > > On Mon, Dec 19, 2016 at 11:02 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 19 Dec 2016, at 22:00, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > > Hi serge > > > > the printing should be normal because like that you are ready to type > > 1/3 + 2/3 and get 1. > > No, not at all: > > 1/3 + 2/3 > > "(7/9)" > > These are all just binary messages evaluated left to right, like this: > > ((1/3) + 2)/3 > > "(7/9)" > > That is why you need the parenthesis in certain contexts. > Now adding two of them is definitively wrong. > > (1/3) + (2/3) > > "1" > > (The first parenthesis are not needed, btw). > > > Now I do not get why you get ((1/2)) thanks for reporting it. > > > > Stef > > > > On Mon, Dec 19, 2016 at 9:08 AM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > I have one question about Fraction. > > > > When I print a fraction like 1/2 in the Playground I obtain (1/2) and > > when I inspect I obtain ((1/2)). Why do we need all these parentheses > > ? > > > > I didn't try with a current Pharo 6.0 image, because my bandwidth is > > quite limited right now (Vietnam). > > > > -- > > Serge Stinckwich > > UCBN & UMI UMMISCO 209 (IRD/UPMC) > > Every DSL ends up being Smalltalk > > http://www.doesnotunderstand.org/ > > > > > > >

Dec. 20, 2016

Re: [Pharo-dev] About Fraction and parentheses

by Stephane Ducasse

I think that I know that :) And this is why I mentioned that if you print 1/3 it prints (1/3) so that we can continue typing + (2/3) On Mon, Dec 19, 2016 at 11:02 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 19 Dec 2016, at 22:00, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > > > Hi serge > > > > the printing should be normal because like that you are ready to type > > 1/3 + 2/3 and get 1. > > No, not at all: > > 1/3 + 2/3 > > "(7/9)" > > These are all just binary messages evaluated left to right, like this: > > ((1/3) + 2)/3 > > "(7/9)" > > That is why you need the parenthesis in certain contexts. > Now adding two of them is definitively wrong. > > (1/3) + (2/3) > > "1" > > (The first parenthesis are not needed, btw). > > > Now I do not get why you get ((1/2)) thanks for reporting it. > > > > Stef > > > > On Mon, Dec 19, 2016 at 9:08 AM, Serge Stinckwich < > serge.stinckwich(a)gmail.com> wrote: > > I have one question about Fraction. > > > > When I print a fraction like 1/2 in the Playground I obtain (1/2) and > > when I inspect I obtain ((1/2)). Why do we need all these parentheses > > ? > > > > I didn't try with a current Pharo 6.0 image, because my bandwidth is > > quite limited right now (Vietnam). > > > > -- > > Serge Stinckwich > > UCBN & UMI UMMISCO 209 (IRD/UPMC) > > Every DSL ends up being Smalltalk > > http://www.doesnotunderstand.org/ > > > > > > >

Dec. 20, 2016

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

by Stephane Ducasse

So what was your crash problem? On Tue, Dec 20, 2016 at 8:43 AM, Alexandre Bergel <alexandre.bergel(a)me.com> 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 > > > > > > On Fri, Dec 16, 2016 at 5:06 PM, Alexandre Bergel < > alexandre.bergel(a)me.com> wrote: > > Okay, tryingâ¦ > > > > Alexandre > > > > > > > On Dec 16, 2016, at 4:40 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> > 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. > > > > > > Cheers, > > > Alex > > > > > > On 16 December 2016 at 16:34, Alexandre Bergel < > alexandre.bergel(a)me.com> wrote: > > > Hi! > > > > > > Vincent and I are experiencing many crashes from GrafPort>copyBits. It > crashes every couple of minutes. > > > > > > I know that not much can be done so far. Stability is my biggest > concern with Pharo :-( > > > I use the latest VM. > > > > > > Cheers, > > > Alexandre > > > > > > > > > > > > > > > > > > > > > -- > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > Alexandre Bergel http://www.bergel.eu > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > _______________________________________________ > > > Moose-dev mailing list > > > Moose-dev(a)list.inf.unibe.ch > > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > > > > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Dec. 20, 2016

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

by Alexandre Bergel

> 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 <alexandre.bergel(a)me.com> wrote: > Okay, tryingâ¦ > > Alexandre > > > > On Dec 16, 2016, at 4:40 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> 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. > > > > Cheers, > > Alex > > > > On 16 December 2016 at 16:34, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Hi! > > > > Vincent and I are experiencing many crashes from GrafPort>copyBits. It crashes every couple of minutes. > > > > I know that not much can be done so far. Stability is my biggest concern with Pharo :-( > > I use the latest VM. > > > > Cheers, > > Alexandre > > > > > > > > > > > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 20, 2016