Skip to content

Leaking file descriptors #122

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

Closed
Yuras opened this issue Apr 3, 2018 · 0 comments · Fixed by #123
Closed

Leaking file descriptors #122

Yuras opened this issue Apr 3, 2018 · 0 comments · Fixed by #123

Comments

@Yuras
Copy link
Contributor

Yuras commented Apr 3, 2018

I got a file descriptor leak on production. Traced to the process library. Basically, creating commutication pipe may fail, and in that case we leak already allocated pipes for stdin, stdout and strerr. The relevant code is here.

Yuras added a commit to Yuras/process that referenced this issue Apr 3, 2018
When we fail to create communication pipe, we should cleanup resources
before exit. E.g. we should close pipes for stdin, stdout and stderr if
they where created. Fixes haskell#122.
Yuras added a commit to Yuras/process that referenced this issue Apr 4, 2018
When we fail to create communication pipe, we should cleanup resources
before exit. E.g. we should close pipes for stdin, stdout and stderr if
they where created. Fixes haskell#122.
Yuras added a commit to Yuras/process that referenced this issue Apr 4, 2018
When we fail to create communication pipe, we should cleanup resources
before exit. E.g. we should close pipes for stdin, stdout and stderr if
they where created. Fixes haskell#122.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant