I bisected it to https://github.com/rakudo/rakudo/commit/40a953f5d9f5c661d8cf9b043643002d348a2000
On earlier rakudo versions it seems to be working fine. I haven't seen it crash once on anything earlier, but it is *very* slow on rakudos that old, so it's hard to tell. nqp changes: https://github.com/perl6/nqp/compare/2016.03-50-g512c9a1...2016.03-57-gbdb13a2 moar changes: https://github.com/MoarVM/MoarVM/compare/2016.03-84-g4afd7b6...2016.03-104-g10d3971 On 2017-05-13 17:00:08, alex.jakime...@gmail.com wrote: > FWIW the problem is still there and is reproducible with the provided > snippet > (just in case somebody is wondering if the issue went away by itself > after > these months). > > On 2017-04-04 06:46:20, scoli...@gmail.com wrote: > > Le Wed, 15 Mar 2017 17:12:00 -0700, alex.jakime...@gmail.com a écrit > > : > > > I am getting errors like: > > > MoarVM panic: Heap corruption detected: pointer 0x7f9a96a5e588 to > > > past > > > fromspace > > > MoarVM panic: Internal error: zeroed target thread ID in work pass > > > > > > Even though it happens when I'm using Gumbo module, my best guess > > > is > > > that it is not its fault. > > > > > > Does not crash that fast with ｢perl6 --optimize=0 …｣, but crashes > > > anyway (you may want to bump up “^100” a little bit for this). > > > > > > Anyway, the code to replicate the issue is shown below. If it gets > > > mangled for some reason, here is a mirror: > > > https://gist.github.com/AlexDaniel/ac7a4d4c49ec8d23e546529976dda67f > > > > > > #!/usr/bin/env perl6 > > > > > > use Gumbo; > > > constant URL = ‘https://perl6.org/community/’; > > > > > > my $response = run(:out, ‘curl’, ‘-s’, URL).out.slurp-rest; > > > for ^100 { > > > .say for parse-html($response).root.elements(:TAG<a>, :RECURSE); > > > } > > > > > > say ‘should've crashed before reaching this’; > > > > I was not able to reproduce it on a 32bit Virtual Machine (debian > > stable) > > Using 2016.11 rakudo and the latest from git. > > Maybe it can be related to how struct size are determined by MoarVM. > >
