We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm seeing sporadic OutOfMemoryErrors caused by the data retained in JvmLocalCache:
JvmLocalCache
The large retention is caused by Gradle internal objects referenced by the line endings policy:
Gradle 8.6 with enabled configuration cache Spotless Gradle 6.25.0 Windows 11
The text was updated successfully, but these errors were encountered:
More specifically, it's the captured FormatExtension in the provider's lambda, so the following hack seems to work around that:
FormatExtension
tasks.withType(SpotlessTask).configureEach { def fixedProvider = provider(LineEnding.UNIX::createPolicy) doFirst { setLineEndingsPolicy(fixedProvider) } }
(setupTask is configured in afterEvaluate, so I needed to override the policy during execution time)
setupTask
afterEvaluate
Sorry, something went wrong.
the captured FormatExtension seems to be a regression introduced by #1777
Don't capture the FormatExtension in LiveCache
2a963f4
Fixed memory leak caused by capturing the Gradle project model referenced by the LineEndings Provider stored in the JvmLocalCache. Fixes diffplug#2067
Successfully merging a pull request may close this issue.
I'm seeing sporadic OutOfMemoryErrors caused by the data retained in
JvmLocalCache
:The large retention is caused by Gradle internal objects referenced by the line endings policy:
Gradle 8.6 with enabled configuration cache
Spotless Gradle 6.25.0
Windows 11
The text was updated successfully, but these errors were encountered: