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
New react + chain syntax locks sometimes #4833
Comments
From pub.claudio@gmail.comHi, The replacement of the 'whatever' syntax as sugar for consuming Channels Attached you'll find 2 scripts: loop_channelreact.p6 reproduces the More info at #perl6 (El_Che and also timotimo). Regards, C. Tested on rakudo 2015.11 on Ubuntu 15.10 and Centos 7.0. |
From @lizmat
Some extra data-points on OS X: - I could not get the channel poll version to break (kept running all night, until at least 300K runs). - the channel react version consistently breaks on the 77th iteration with a SIGABRT - running the channel react version with MVM_SPESH_DISABLE=1, makes it consistently break on the 70th iteration with a SIGABRT - running it with MVM_JIT_DISABLE=1 makes no difference from not specifying it: it breaks on the 77th iteration with a SIGABRT Changing the whenever {} to: whenever $channel -> \val { makes it consistently fail on the 75th iteration All in all, this leads me to suspect some kind of garbage collect issue. And indeed, if I put an "nqp::force_gc" just before the “sleep”, it does not seem to fail (still running) Liz |
The RT System itself - Status changed from 'new' to 'open' |
From @jnthnOn Tue, 08 Dec 2015 05:40:29 -0800, pub.claudio@gmail.com wrote:
All kinds of things have been fixed that could have been to blame since this ticket was field; either way, it works out. I remove the sleep so it'd go faster and ran it for 250,000 iterations without trouble. Added this example as a test in S17-supply/syntax.t to make sure it doesn't come up again. |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#126842 (status was 'resolved')
Searchable as RT126842$
The text was updated successfully, but these errors were encountered: