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
writing more than 8192 bytes to IO::Handle causes it to hang forever #5169
Comments
From @LLFournperl6 -e 'my If you swap I made RT #127681 ( which is the same thing and can be closed ) today. But |
From @usev6FWIW that hangs on FreeBSD as well (maybe not too much a surprise, given the relationship of the OSes). |
1 similar comment
From @usev6FWIW that hangs on FreeBSD as well (maybe not too much a surprise, given the relationship of the OSes). |
From @usev6On Fri, 10 Feb 2017 23:48:54 -0800, bartolin@gmx.de wrote:
This still hangs on MoarVM, but works on JVM (I didn't check the behaviour on JVM last year): $ ./perl6-j -e 'my alive |
The RT System itself - Status changed from 'new' to 'open' |
From @usev6On Fri, 10 Feb 2017 23:48:54 -0800, bartolin@gmx.de wrote:
Hmm, looks like it hangs on Linux too -- with more than 224000 bytes on my machine: $ perl6 -e 'my |
From @timoThis is a well-known problem in IPC. If you don't do it async, you risk Wouldn't call this a rakudo bug. On 07/03/18 23:04, Christian Bartolomaeus via RT wrote:
|
From @geekosaurAnd in the cases where it "works", the buffer is larger. Which runs the Perl 5 and Python both call this the open3 problem. On Wed, Mar 7, 2018 at 6:42 PM, Timo Paulssen <timo@wakelift.de> wrote:
-- |
From @LLFournWhen I filed this ticket I kinda expected that somehow rakudo or libuv Consider: $ perl6 -e 'my Using .get instead of slurp-rest works fine. This suggested to me that perl6 -e 'my But for some reason, just sleeping didn't: perl6 -e 'my I'd say this is closable. The solution is to wait for the process to exit Thanks! On Thu, Mar 8, 2018 at 2:51 PM Brandon Allbery via RT <
|
Migrated from rt.perl.org#127682 (status was 'open')
Searchable as RT127682$
The text was updated successfully, but these errors were encountered: