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
await
ing a Promise in a different thread sometimes hangs
#3503
Comments
From @lizmat(since leont has been so busy with other stuff, I thought to report the problem he found) 12:11 * leont suspects he's observing Promise.allof spinlocking or some such. 100% CPU usage, but no input is coming in :-/ |
From @cokeOn Fri Sep 05 14:44:06 2014, elizabeth wrote:
This seems to work with no issue here. Is this ticket closable? $ perl6 -e 'my $waiter = Proc::Async.new(:path("echo"), :args(<Hello World>)).start; await start { await $waiter };' -- |
The RT System itself - Status changed from 'new' to 'open' |
From @LLFournNot sure if it's relevant here but last time I checked there is an issues RT #125758 for example which looks similar to this.
|
From @LLFournNow I'm at home I tried it on my Mac, I can confirm that: perl6 -e 'my $waiter = Proc::Async.new(:path<echo>, :args<Hello prints Hello World and then hangs forever. On Wed, Apr 27, 2016 at 2:58 PM Lloyd Fournier <lloyd.fourn@gmail.com>
|
From @cokeOn Wed Apr 27 03:02:14 2016, lloyd.fourn@gmail.com wrote:
Can you include the output of sw_vers and perl6 --version ? -- |
From @smlsFor me, the command sometimes hangs and sometimes doesn't. This is on up-do-date Rakudo: ➜ uname -srm |
From @LLFournIt works now! whoever fixed it++. Close this! (and #125758). On Mon, May 2, 2016 at 11:34 PM Will Coleda via RT <
|
From @lizmatFWIW, I think it was 1ee27e660a8dce3ae
|
From @smlsNo, this one-liner... perl6 -e 'my $waiter = Proc::Async.new(:path<echo>, :args<Hello World>).start; await start { await $waiter }' ...still occasionally hangs for me on the latest Rakudo nom: This is Rakudo version 2016.04-117-g7db7b46 built on MoarVM version 2016.04 But it does appear to happen more seldomly now. |
From @jnthnOn Fri May 06 06:54:52 2016, smls75@gmail.com wrote:
I can still reproduce it too; seems that occasionally the scheduler starts too few threads (in fact, only one, and that is tied up with the await, and so nothing processes the incoming message saying the process ended). |
From @jnthnOn Wed, 03 Aug 2016 12:23:32 -0700, jnthn@jnthn.net wrote:
The new scheduler merged a couple weeks back addresses this; added a test in S17-procasync/stress.t. |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#122709 (status was 'resolved')
Searchable as RT122709$
The text was updated successfully, but these errors were encountered: