-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GC related crash on repeated sleepsort (using Channel) #5255
Comments
From marcus.ramberg@usit.uio.noFrom #perl6 marcusramberg <http://dogfood.convos.by/freenode/marcusramberg> 17:13 17:13 |
From @jonathanstoweThe code: sub sleep_sort (*@list where .all >= 0) { my $channel = Channel.new; await @list.map: -> $delay { }; $channel.close; return $channel.list; say sleep_sort(3,2,1,5,4) for (1 ... 10000); And gives rise to this back trace: This is Rakudo version 2016.03-135-gbaf8ac3 built on MoarVM version 2016.03-108-gca1a21a |
The RT System itself - Status changed from 'new' to 'open' |
From @lizmat[2016-04-22T16:08:20+0100] <marcusramberg> Listening to Damian talk about concurrency in Oslo, and I tried one of his examples, but it seems to crash perl6 when you try to run it for some iterations - https://gist.github.com/marcusramberg/f789306f4f580c6cf1270ca12a333391 The code in question:sub sleep_sort (*@list where .all >= 0) { my $channel = Channel.new; await @list.map: -> $delay { }; $channel.close; return $channel.list; say sleep_sort(3,2,1,5,4) for (1 ... 10000); |
From @jonathanstoweLooks like this isn't failing with This is Rakudo version 2016.04-36-gce5dc00 built on MoarVM version 2016.04 Probably some test to close. |
From @lizmat
No, please keep this open, as this was only fixed by essentially a workaround: Channel.Supply.list still fails in the same way. Liz |
From marcus.ramberg@usit.uio.no
yay |
From @jnthnOn Fri Apr 22 08:55:46 2016, jns+bc@gellyfish.co.uk wrote:
Looks like the mutex missing unlock bug that I fixed in Rakudo commit 48c2af6d059. Also, I've run the code in question (all 10,000 iterations of it) a bunch of times and not seen any failures. For good measure, I've also added it as a stress test in S17-channel/stress.t. /jnthn |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#127960 (status was 'resolved')
Searchable as RT127960$
The text was updated successfully, but these errors were encountered: