There is a new Pharo build available!
The status of the build #553 was: FAILURE. The Pull Request #888 was integrated: "20941-deprecate-theMetaclass-and-the-theNonMeta" Pull request url: https://github.com/pharo-project/pharo/pull/888 Issue Url: https://pharo.fogbugz.com/f/cases/20941 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/553/ |
FAILURE due to VM crash: [32] replaceFrom:to:with:startingAt: [32] replaceFrom:to:with:startingAt: [32] replaceFrom:to:with:startingAt: [32] basicIdentityHash [32] replaceFrom:to:with:startingAt: [32] replaceFrom:to:with:startingAt: [32] new: [32] new: [32] [32] stack page bytes 4096 available headroom 2788 minimum unused headroom 156 [32] [32] (Segmentation fault) [32] ./vm/pharo: line 11: 13443 Aborted "$DIR"/"pharo-vm/pharo" --nodisplay "$@" |
Hi, I have already checked this error. The error is random in the development branch, although in my branch is happening always. I have detected that the problem is that the GC is corrupting the the objects when it has to enlarge the Eden. This problem also was detected some months ago by Pavel when he tried to load a big baseline (Seaside in that moment). I have solved it in a similar way, increasing the Eden size before loading BaselineOfIDE. Since this "hack" my branch is running normally (well... it has other problems with some tests... but that is expected). Maybe Clement can through more light to the matter. Cheers, On Fri, Feb 16, 2018 at 12:50 PM, Marcus Denker <[hidden email]> wrote:
Pablo Tesone.
[hidden email] |
Could we make that the default?
|
In reply to this post by tesonep@gmail.com
On Fri, Feb 16, 2018 at 2:07 PM, [hidden email] <[hidden email]> wrote:
> Hi, I have already checked this error. > > The error is random in the development branch, although in my branch is > happening always. > I have detected that the problem is that the GC is corrupting the the > objects when it has to enlarge the Eden. > > This problem also was detected some months ago by Pavel when he tried to > load a big baseline (Seaside in that moment). > I have solved it in a similar way, increasing the Eden size before loading > BaselineOfIDE. > > Since this "hack" my branch is running normally (well... it has other > problems with some tests... but that is expected). > Maybe Clement can through more light to the matter. > Hi, On what VM is this happening? For linux 64bits vm I get a lot a random crash during configuration loading. But these crash vanish when using the latest Pharo 70 vm for linux 64bits. > Cheers, > > > > -- > Pablo Tesone. > [hidden email] -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France |
Hi Cyril, I cannot say nothing about problems in 64bits. Try creating a bigger Eden, you should run Smalltalk vm parameterAt: 45 put: (Smalltalk vm parameterAt: 44) * 4 The changes are only effected in the next loading of the image, so you should do something like: ./pharo "Pharo.image" eval --save "Smalltalk vm parameterAt: 45 put: (Smalltalk vm parameterAt: 44) * 4" And then try to load the configuration. Marcus, I am opening an issue for that. Cheers, On Fri, Feb 16, 2018 at 3:57 PM, Cyril Ferlicot <[hidden email]> wrote: On Fri, Feb 16, 2018 at 2:07 PM, [hidden email] <[hidden email]> wrote: Pablo Tesone.
[hidden email] |
In reply to this post by CyrilFerlicot
Hi Cyril,
On 16 February 2018 at 15:57, Cyril Ferlicot <[hidden email]> wrote: > > On what VM is this happening? > > For linux 64bits vm I get a lot a random crash during configuration > loading. But these crash vanish when using the latest Pharo 70 vm for > linux 64bits. Would you mind posting the output of "pharo --version" so I can try with exactly the same 64bit VM? Thanks! Alistair |
On Fri, Feb 16, 2018 at 4:26 PM, Alistair Grant <[hidden email]> wrote:
> Hi Cyril, > > On 16 February 2018 at 15:57, Cyril Ferlicot <[hidden email]> wrote: >> >> On what VM is this happening? >> >> For linux 64bits vm I get a lot a random crash during configuration >> loading. But these crash vanish when using the latest Pharo 70 vm for >> linux 64bits. > > Would you mind posting the output of "pharo --version" so I can try > with exactly the same 64bit VM? Hi, I moved our script to use the latest Pharo 70 vm but it was with the vm we get via curl https://get.pharo.org/64/61+vm | bash It downloads a linux vm from july 2017. Crash happen around 50% of the time with a segfault on our Jenkins. We have a lot of dependencies such as Famix, Seaside, MDL... So the configurations bring *a lot* of things. I don't know if it will crash as much with smaller configurations. I cannot share what we use since it is close code. > > Thanks! > Alistair > -- Cyril Ferlicot https://ferlicot.fr |
Hi Cyril,
On 16 February 2018 at 16:59, Cyril Ferlicot <[hidden email]> wrote: > On Fri, Feb 16, 2018 at 4:26 PM, Alistair Grant <[hidden email]> wrote: >> Hi Cyril, >> >> On 16 February 2018 at 15:57, Cyril Ferlicot <[hidden email]> wrote: >>> >>> On what VM is this happening? >>> >>> For linux 64bits vm I get a lot a random crash during configuration >>> loading. But these crash vanish when using the latest Pharo 70 vm for >>> linux 64bits. >> >> Would you mind posting the output of "pharo --version" so I can try >> with exactly the same 64bit VM? > > > Hi, > > I moved our script to use the latest Pharo 70 vm but it was with the > vm we get via > > curl https://get.pharo.org/64/61+vm | bash > > It downloads a linux vm from july 2017. > > Crash happen around 50% of the time with a segfault on our Jenkins. We > have a lot of dependencies such as Famix, Seaside, MDL... So the > configurations bring *a lot* of things. I don't know if it will crash > as much with smaller configurations. I cannot share what we use since > it is close code. In your original message you said that the latest Pharo 7 64bit VM isn't crashing. Can you provide the version information for that one? Thanks, Alistair |
Free forum by Nabble | Edit this page |