May 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Crash on GC garbageCollect

by Eliot Miranda

Hi Andreas, On Fri, May 25, 2018 at 1:24 AM, Andreas Brodbeck <dassi(a)mindclue.ch> wrote: > Hi all > > I have a 6.0 image which crashes on garbage collect. If I run "Smalltalk > garbageCollect" it crashes. The crash log is attached. But I don't really > understand that crash log. I run it with a 6.0 VM, tried it also with > newest 6.1 VM and 7.0 VM, but always the same error. > > I read here in the list about crash problems with GC, memory leaks and > similar, but I really don't see what I could do. > Note that if you build an Assert VM you will be able to manually patch the image in lldb so that you can rescue it. It looks like this: $ *lldb PharoAssert.app/Contents/MacOS/Pharo* (lldb) target create "/Users/eliot/oscogvm/build.macos64x64/pharo.cog.spur/ PharoAssert.app/Contents/MacOS/Pharo" Current executable set to '/Users/eliot/oscogvm/build. macos64x64/pharo.cog.spur/PharoAssert.app/Contents/MacOS/Pharo' (x86_64). (lldb) settings set -- target.run-args "clap_broken.d9e5daa.image" (lldb) *b warning* Breakpoint 1: 3 locations. (lldb) *run --leakcheck 31 clap_broken.d9e5daa.image* Process 31569 launched: '/Users/eliot/oscogvm/build. macos64x64/pharo.cog.spur/PharoAssert.app/Contents/MacOS/Pharo' (x86_64) object leak in *0x10f919658* @ 0 = 0x122216538 object leak in *0x10fbb3448* @ 0 = 0x122216760 object leak in *0x10fbb3480* @ 0 = 0x1222166a8 object leak in *0x10ff384f0* @ 0 = 0x122d480b0 object leak in *0x10ff38518* @ 0 = 0x122d480b0 object leak in *0x10ff385d0* @ 0 = 0x122d480b0 Process 31569 stopped * thread #1: tid = 0x5b6d56, 0x0000000100001a83 Pharo`warning(s=" checkHeapIntegrityclassIndicesShouldBeValid(0, 1) 57196") + 19 at gcc3x-cointerp.c:44, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1 frame #0: 0x0000000100001a83 Pharo`warning(s=" checkHeapIntegrityclassIndicesShouldBeValid(0, 1) 57196") + 19 at gcc3x-cointerp.c:44 41 sqInt warnpid, erroronwarn; 42 void 43 warning(char *s) { /* Print an error message but don't necessarily exit. */ -> 44 if (erroronwarn) error(s); 45 if (warnpid) 46 printf("\n%s pid %ld\n", s, (long)warnpid); 47 else (lldb) *call freeObject(0,0x10f919658)* (sqInt) $0 = 4478138592 (lldb) *call **freeObject**(0,0x10fbb3448)* (sqInt) $1 = 4478138592 (lldb) *call **freeObject**(0,0x10fbb3480)* (sqInt) $2 = 4478138592 (lldb) *call **freeObject**(0,0x10ff384f0)* (sqInt) $3 = 4478138592 (lldb) *call **freeObject**(0,0x10ff38518)* (sqInt) $4 = 4478138592 (lldb) *call **freeObject**(0,0x10ff385d0)* (sqInt) $5 = 4478138592 (lldb) *expr checkForLeaks = 0* (sqInt) $0 = 0 (lldb) *continue* and then save the image. > > Any pointers in which direction I could investigate? > > Thanks and cheers, > Andreas > > -- > Andreas Brodbeck > www.mindclue.ch > > > -- _,,,^..^,,,_ best, Eliot

May 25, 2018

[Pharo 7.0-dev] Build #954: 21916-OSWindow-SDL2-leaks-because-there-are-strong-references-on-OSSDL2WindowHandle

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #954 was: FAILURE. The Pull Request #1369 was integrated: "21916-OSWindow-SDL2-leaks-because-there-are-strong-references-on-OSSDL2WindowHandle" Pull request url: https://github.com/pharo-project/pharo/pull/1369 Issue Url: https://pharo.fogbugz.com/f/cases/21916 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 25, 2018

Re: [Pharo-dev] Crash on GC garbageCollect

by Esteban Lorenzano

> On 25 May 2018, at 23:48, Stephan Eggermont <stephan(a)stack.nl> wrote: > > Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: >> thatâs because 6.1 images still comes with an old VM. >> I think I will backport the newer, but next week (testing time has passed, I think). > > You probably want to include the TLS fix from this week for Win7 so github > repos eork no I do not want :) because in that case I will need to repeat the full cycle: 2 weeks as latest, one month as stable in 7.0, than backport. and probably in that moment there will be another fix to include. So, I will promote this one, and then we can start the next cycle :) Esteban > > Stephan > > > >

May 25, 2018

Re: [Pharo-dev] Crash on GC garbageCollect

by Stephan Eggermont

Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > thatâs because 6.1 images still comes with an old VM. > I think I will backport the newer, but next week (testing time has passed, I think). You probably want to include the TLS fix from this week for Win7 so github repos eork Stephan

May 25, 2018

Re: [Pharo-dev] Beacon for Pharo 7

by Stephan Eggermont

Norbert Hartl <norbert(a)hartl.name> wrote: > Really?? Donât you think the overhead is massive compared to the gain? As long as the baselines are nice trees, described only one level deep, it should be ok-ish. That never seems to be the case though, and as soon as you get diamond dependency issues the duplication of volatile information creates a lot of commit ripple Iâd would like to see a description of how that is supposed to work with all the duplicated baselines and repos. Stephan

May 25, 2018

[Pharo 7.0-dev] Build #953: 21983-Fixing-Slot-propagation-in-Traits-Tests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #953 was: SUCCESS. The Pull Request #1425 was integrated: "21983-Fixing-Slot-propagation-in-Traits-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1425 Issue Url: https://pharo.fogbugz.com/f/cases/21983 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 25, 2018

Re: [Pharo-dev] Beacon for Pharo 7

by Norbert Hartl

Really?? Donât you think the overhead is massive compared to the gain? Norbert > Am 25.05.2018 um 21:08 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > Hi, > > Yes, we want to have the concrete loggers managed with separate baselines. I would also put them in individual repositories. > > Cheers, > Doru > > >> On May 25, 2018, at 5:58 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> >> >> 2018-05-25 17:21 GMT+03:00 Stephan Eggermont <stephan(a)stack.nl>: >> Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >>> Hi. >>> >>> I was looking at Beacon again to prepare integration. Some changes was >>> needed in baseline for better granularity. So I send pull request because I >>> have no permissions. >>> >>> But now I remember that we had idea to integrate only core part of Beacon >>> which requires MemoryLogger and TranscriptLogger. And we wanted to manage >>> logger backends using separate baselines. So we need separate repos to have >>> separate versioning. >> >> Why would you want separate baselines for that? And on top of that separate >> repos? >> >> Because when you will fix or improve Beacon-SysLog you will probably do not want to update Beacon-Core version which will force you to update Pharo (where SysLog is not loaded). >> >> >> Stephan > > -- > www.tudorgirba.com > www.feenk.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > > >

May 25, 2018

Re: [Pharo-dev] Crash on GC garbageCollect

by Esteban Lorenzano

thatâs because 6.1 images still comes with an old VM. I think I will backport the newer, but next week (testing time has passed, I think). cheers, Esteban > On 25 May 2018, at 17:02, Ben Coman <btc(a)openInWorld.com> wrote: > > There was a period where a new GC algorithm had some teething issues, but those were resolved. > Where did you get the newest VMs? > The one from your report seems old... "VM: 201708271955" > > What platform are you on? > How are your starting your Image? > > Can you move your development to a fresh download of latest 6.1 Image & VM and report if that has any problems? > http://pharo.org/download <http://pharo.org/download> > > HTH > cheers -ben > > On 25 May 2018 at 16:24, Andreas Brodbeck <dassi(a)mindclue.ch <mailto:dassi@mindclue.ch>> wrote: > Hi all > > I have a 6.0 image which crashes on garbage collect. If I run "Smalltalk garbageCollect" it crashes. The crash log is attached. But I don't really understand that crash log. I run it with a 6.0 VM, tried it also with newest 6.1 VM and 7.0 VM, but always the same error. > > I read here in the list about crash problems with GC, memory leaks and similar, but I really don't see what I could do. > > Any pointers in which direction I could investigate? > > Thanks and cheers, > Andreas > > -- > Andreas Brodbeck > www.mindclue.ch <http://www.mindclue.ch/> > > >

May 25, 2018

Re: [Pharo-dev] Beacon for Pharo 7

by Tudor Girba

Hi, Yes, we want to have the concrete loggers managed with separate baselines. I would also put them in individual repositories. Cheers, Doru > On May 25, 2018, at 5:58 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > 2018-05-25 17:21 GMT+03:00 Stephan Eggermont <stephan(a)stack.nl>: > Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > Hi. > > > > I was looking at Beacon again to prepare integration. Some changes was > > needed in baseline for better granularity. So I send pull request because I > > have no permissions. > > > > But now I remember that we had idea to integrate only core part of Beacon > > which requires MemoryLogger and TranscriptLogger. And we wanted to manage > > logger backends using separate baselines. So we need separate repos to have > > separate versioning. > > Why would you want separate baselines for that? And on top of that separate > repos? > > Because when you will fix or improve Beacon-SysLog you will probably do not want to update Beacon-Core version which will force you to update Pharo (where SysLog is not loaded). > > > Stephan -- www.tudorgirba.com www.feenk.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

May 25, 2018

[Pharo 7.0-dev] Build #952: added an example to the method '->'

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #952 was: FAILURE. The Pull Request #1427 was integrated: "added an example to the method '->'" Pull request url: https://github.com/pharo-project/pharo/pull/1427 Issue Url: https://pharo.fogbugz.com/f/cases/20315 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 25, 2018