-
Notifications
You must be signed in to change notification settings - Fork 117
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
Potentially lingering opened files #1124
Comments
lefou
changed the title
Potential lingering opened files
Potentially lingering opened files
Sep 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Mill, where we use Zinc to compile Java and Scala sources, we recently tried to find the source for some left-over opened files, which produce issues for processes on Windows. We analyzed a specific compile run with https://github.com/jenkinsci/lib-file-leak-detector and found left over opened files (com-lihaoyi/mill#1939 (comment)). Non of them were directly opened by Mill but sbt/zinc instead, so I though, I report it here. I hope, you find it useful.
In the Details, you can find the stacktraces of the opened files:
The opened file is always
C:\projects\sake\mill\out\main\moduledefs\jar.dest\out.jar
, which is a locally built compiler plugin. It is subseqently used in other build targets, so my suspicion is, that zinc is not properly closing such compiler plugin resources. This is probably a rather rare situation, so it could be also an older issue which went unnoticed for a very long time.The text was updated successfully, but these errors were encountered: