November 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] two issues: GC and wrong pointers

by ducasse

May be we have two problems then :( Because we have problem without a large image. Stef > On 11 Nov 2019, at 14:44, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > For the GC problem from https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391, there is no threading involved. Just invoking full GC in a large image. > > Cheers, > Doru > > > >> On Nov 11, 2019, at 1:47 PM, ducasse <stepharo(a)netcourrier.com> wrote: >> >> Hi doru >> >> >> Can you tell us more? How many threads are running? how many times did you save the image? >> Pablo is investigating a bug related to the GC that happens when we have many threads and saved the image >> multiple times. He was on it since a couple of days. >> >> Now Pablo is attending Smalltalks and will be on vacation until end of the month. >> Guille is on father leave and coming back to work one day a week. >> >> So we are concerned about this problem but we cannot really allocate people on it before beginning of december. >> >> S. >> >>> On 11 Nov 2019, at 12:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> During our work we encountered two issues we think should be considered critical. >>> >>> The first is that the garbage collector is unreliable on larger images: >>> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 >>> We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. >>> >>> The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: >>> https://github.com/pharo-project/pharo/issues/4967 >>> This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. >>> >>> Would anyone be available for a collaboration in the following days? >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> feenk.com >>> >>> "Not knowing how to do something is not an argument for how it cannot be done." >>> >>> >> >> >> > > -- > feenk.com > > "Value is always contextual." > > > > > > >

Nov. 11, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by Marcus Denker

>>> >>> Hi, >>> >>> During our work we encountered two issues we think should be considered critical. >>> >>> The first is that the garbage collector is unreliable on larger images: >>> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 >>> We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. >>> >>> The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: >>> https://github.com/pharo-project/pharo/issues/4967 >>> This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. >>> I think my PR fixes itâ¦ the PR is green and the downloaded artefact seems to not show any problematic methods anymore: https://github.com/pharo-project/pharo/pull/5120 <https://github.com/pharo-project/pharo/pull/5120> Marcus

Nov. 11, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by Tudor Girba

Hi, For the GC problem from https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391, there is no threading involved. Just invoking full GC in a large image. Cheers, Doru > On Nov 11, 2019, at 1:47 PM, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi doru > > > Can you tell us more? How many threads are running? how many times did you save the image? > Pablo is investigating a bug related to the GC that happens when we have many threads and saved the image > multiple times. He was on it since a couple of days. > > Now Pablo is attending Smalltalks and will be on vacation until end of the month. > Guille is on father leave and coming back to work one day a week. > > So we are concerned about this problem but we cannot really allocate people on it before beginning of december. > > S. > >> On 11 Nov 2019, at 12:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> During our work we encountered two issues we think should be considered critical. >> >> The first is that the garbage collector is unreliable on larger images: >> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 >> We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. >> >> The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: >> https://github.com/pharo-project/pharo/issues/4967 >> This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. >> >> Would anyone be available for a collaboration in the following days? >> >> Cheers, >> Doru >> >> >> -- >> feenk.com >> >> "Not knowing how to do something is not an argument for how it cannot be done." >> >> > > > -- feenk.com "Value is always contextual."

Nov. 11, 2019

[Pharo 8.0] Build #970: bind on collections

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

There is a new Pharo build available! The status of the build #970 was: FAILURE. The Pull Request #5108 was integrated: "bind on collections" Pull request url: https://github.com/pharo-project/pharo/pull/5108 Issue Url: https://github.com/pharo-project/pharo/issues/collectoinBind Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 11, 2019

[Pharo 8.0] Build #969: 4337-tests-of-RB-should-not-use-category-based-class-definition-but-package

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

There is a new Pharo build available! The status of the build #969 was: FAILURE. The Pull Request #5106 was integrated: "4337-tests-of-RB-should-not-use-category-based-class-definition-but-package" Pull request url: https://github.com/pharo-project/pharo/pull/5106 Issue Url: https://github.com/pharo-project/pharo/issues/4337 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 11, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by ducasse

Hi doru Can you tell us more? How many threads are running? how many times did you save the image? Pablo is investigating a bug related to the GC that happens when we have many threads and saved the image multiple times. He was on it since a couple of days. Now Pablo is attending Smalltalks and will be on vacation until end of the month. Guille is on father leave and coming back to work one day a week. So we are concerned about this problem but we cannot really allocate people on it before beginning of december. S. > On 11 Nov 2019, at 12:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > During our work we encountered two issues we think should be considered critical. > > The first is that the garbage collector is unreliable on larger images: > https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 > We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. > > The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: > https://github.com/pharo-project/pharo/issues/4967 > This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. > > Would anyone be available for a collaboration in the following days? > > Cheers, > Doru > > > -- > feenk.com > > "Not knowing how to do something is not an argument for how it cannot be done." > >

Nov. 11, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by Marcus Denker

> On 11 Nov 2019, at 12:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > During our work we encountered two issues we think should be considered critical. > > The first is that the garbage collector is unreliable on larger images: > https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 > We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. > > The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: > https://github.com/pharo-project/pharo/issues/4967 > This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. > This one I want to have a look atâ¦ I think the solution is to remove the magic and maybe even think about integrating the FFI plugin into the compiler. I am available Tuesday afternoon. Marcus

Nov. 11, 2019

two issues: GC and wrong pointers

by Tudor Girba

Hi, During our work we encountered two issues we think should be considered critical. The first is that the garbage collector is unreliable on larger images: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: https://github.com/pharo-project/pharo/issues/4967 This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. Would anyone be available for a collaboration in the following days? Cheers, Doru -- feenk.com "Not knowing how to do something is not an argument for how it cannot be done."

Nov. 11, 2019

[Pharo 8.0] Build #968: 5087-Fuel-should-be-out-of-Morphic-baseline-

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

There is a new Pharo build available! The status of the build #968 was: SUCCESS. The Pull Request #5095 was integrated: "5087-Fuel-should-be-out-of-Morphic-baseline-" Pull request url: https://github.com/pharo-project/pharo/pull/5095 Issue Url: https://github.com/pharo-project/pharo/issues/5087 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 11, 2019

[Pharo 8.0] Build #967: Some-cleanings-on-protocols

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

There is a new Pharo build available! The status of the build #967 was: FAILURE. The Pull Request #5115 was integrated: "Some-cleanings-on-protocols" Pull request url: https://github.com/pharo-project/pharo/pull/5115 Issue Url: https://github.com/pharo-project/pharo/issues/Some Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 11, 2019