Run Android Lint in its own JVM - #127
Merged
Merged
Conversation
In-process lint kept growing the Gradle daemon heap across runs until builds stalled in garbage collection; android.experimental.runLintInProcess =false keeps the daemon small. Same change as scalelite-android.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Lint running inside the Gradle daemon grew the heap by hundreds of MB per run until a build sat in garbage collection for 25 minutes (seen on this repo today).
android.experimental.runLintInProcess=falsemoves lint to its own JVM; the daemon stays small and a warm build is back to seconds. Same line as in scalelite-android so the threegradle.propertiesstay identical.