-
Notifications
You must be signed in to change notification settings - Fork 4.9k
gradle-worker-classpath never cleaned up (polluting temp) #12020
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
Comments
I have over 700 |
Well, yes -- the above snippet I included is wrong. :) No mystery about it. |
FYI this bug is rather serious, at least for my use case. I discovered my Is the above snippet easy to fix? Hmm, the snippet looks wrong, because the source has presumably changed since @dweiss opened this issue. @dweiss is it possible to link to a stable source (to a specific githash) instead? |
it's still the same code area -- temporary file creation without proper deletion. |
@adammurdoch Just pinging to bring your attention to this issue - would you happen to know if it's a bug or a feature we can somehow avoid? |
Similar issue occurs with tests - this time they leave behind temp files under the task's tmp, which is at least project-local. Lines 42 to 47 in c626475
Related Lucene issues: |
Any workaround for this one? |
I've encountered the same issue. Our CI machine's disk filled up with garbage files (15G ) |
For anyone still suffering from this problem, here's a simple gradle task kludge I've been using as a workaround:
|
This issue is still biting me (Gradle 8.10 on Arch Linux 6.12.4-arch1-1) .. I now have ~93 K of these leftover files from gradle:
I will remove them manually but the root cause bug really should be fixed? |
Sorry for the late reply. This issue will be closed as a duplicate of Please add your use case and 👍 to that issue. If you think our analysis is wrong, please provide us with more detailed information explaining why. |
Uh oh!
There was an error while loading. Please reload this page.
Classpath passed via options file is never cleaned up from temp.
https://github.com/gradle/gradle/blob/master/subprojects/core/src/main/java/org/gradle/process/internal/worker/child/ApplicationClassesInSystemClassLoaderWorkerImplementationFactory.java#L100
This creates literally hundreds of files on each build for large, multi-module projects.
Is there any workaround? This is really annoying.
The text was updated successfully, but these errors were encountered: