You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running BCV tasks, Gradle doesn’t free up metaspace memory.
For example, in the Ktor project, each run of apiDump uses up to 4GB of metaspace memory (#281). The only way to free up this memory is to restart Gradle Daemon.
Here is an example of four consecutive launches of ./gradlew apiDump --rerun-tasks in the Ktor project.
After running BCV tasks, Gradle doesn’t free up metaspace memory.
For example, in the Ktor project, each run of
apiDump
uses up to 4GB of metaspace memory (#281). The only way to free up this memory is to restart Gradle Daemon.Here is an example of four consecutive launches of
./gradlew apiDump --rerun-tasks
in the Ktor project.It is a known Gradle bug:
Steps to reproduce
./gradlew apiDump --rerun-tasks
several timesPossible workaround
Some projects use
processIsolation
instead ofclassLoaderIsolation
(cortinico/ktfmt-gradle#206, sigstore/sigstore-java#283). Could this solution be used for BCV?The text was updated successfully, but these errors were encountered: