Fix gradle properties to avoid out of memory #7173
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wmontwe
force-pushed
the
fix_gradle_properties
branch
from
428f22d to
57580f2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to #19750 the Gradle Daemon could disapear or run out of memory when
org.gradle.jvmargshas been altered in thegradle.properties. This causes the deamon to drop all default values leavingXX:MaxMetaspaceSizeunbound which consumes more and more memory.This should fix the issues until #19750 is fixed.
Here are the default values used by the Gradle Daemon: DaemonParameters.
For our project the default memory settings have been multiplied by 4.