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
Proc::Async.bind-stdin leaves a unix socket open #6461
Comments
From shoichikaji@gmail.com(Please note that the following is available at gist too. I found that Proc::Async.bind-stdin left a unix socket open. ## How to reproduce this issue The following script demonstrates this ❯ perl6 bind-stdin-test.p6 20 >/dev/null This shows everytime we call bind-stdin method, the number of open The output of lsof -p PID in macos is below: ... See https://gist.github.com/skaji/b0b210304e932445890f2a28cf7f53b0#file-zz-result-on-macos-txt ## My environment * This is Rakudo version 2017.07-202-ge3e29c5 built on MoarVM version |
From @skidsOn Mon, 21 Aug 2017 04:38:48 -0700, shoichikaji@gmail.com wrote:
I've been able to confirm that the particular file handles being leaked I don't see anything else in the Proc::Async API that would help to close these Internally, handles are fed to a uv_process_t. This libuv object has a uv_close, Note that if we are (unlike in the example) interested in the output of the The Proc::Async class and its associated MoarVM backend are pretty convoluted code - @blockers.push( ...but that supposes a lot of things are safe to do which probably are not safe to do. |
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#131940 (status was 'open')
Searchable as RT131940$
The text was updated successfully, but these errors were encountered: