-
Notifications
You must be signed in to change notification settings - Fork 21
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
Using sys.process results in file descriptor leaks #5439
Comments
Imported From: https://issues.scala-lang.org/browse/SI-5439?orig=1 |
@dcsobral said: [partest] java.io.IOException: Stream closed
[partest] at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:145)
[partest] at java.io.BufferedInputStream.read1(BufferedInputStream.java:255)
[partest] at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
[partest] at java.io.FilterInputStream.read(FilterInputStream.java:90)
[partest] at scala.sys.process.BasicIO$.loop$1(BasicIO.scala:115)
[partest] at scala.sys.process.BasicIO$.transferFullyImpl(BasicIO.scala:122)
[partest] at scala.sys.process.BasicIO$.transferFully(BasicIO.scala:104)
[partest] at scala.sys.process.ProcessImpl$PipeThread.runloop(ProcessImpl.scala:159)
[partest] at scala.sys.process.ProcessImpl$PipeSource.run(ProcessImpl.scala:180)
|
@adriaanm said: |
@acruise said: |
@dcsobral said: Fixed by 838c97bcb55908aff3638caae0aa87d237100b4b. |
@dcsobral said: |
@lrytz said: |
@dcsobral said: |
@lrytz said: |
@acruise said: |
@lrytz said: |
Using
scala.sys.process
results in file descriptor leaks in the form of pipes used internally by the library. For most usages, there's no workaround possible.The issue is that the streams associated with each
SimpleProcesss
are not closed, and the user can't get at them. This issue has been fixed on SBT, but that fix results in another bug. I'm investigating the issue.The text was updated successfully, but these errors were encountered: