Skip to content

ci(android): give the Kotlin compile daemon its own heap #801

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.

Sign up for GitHub

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

Merged
ryanbr merged 1 commit into from
Jul 25, 2026
Merged

ci(android): give the Kotlin compile daemon its own heap #801

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions android/gradle.properties
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,16 @@
# JVM args for the Gradle daemon. 2g heap + file encoding is enough for this single-module app.
org.gradle.jvmargs=-Xmx2048m -Dfile.encoding=UTF-8

# Heap for the KOTLIN COMPILE DAEMON, which is a separate process from the Gradle daemon above and
# does NOT inherit org.gradle.jvmargs. Unset, it takes a default that the Compose compiler plugin
# outgrew: compileFullReleaseKotlin died with `java.lang.OutOfMemoryError: Java heap space` inside
# androidx.compose.compiler.plugins.kotlin.lower.ComposerTypeRemapper while the debug variant built
# fine, because the release variant's extra lowering passes push the IR deep-copy over the limit.
# Gradle's own failure hint names this exact property. Raised here rather than lifting
# org.gradle.jvmargs so peak memory stays reasonable on a contributor's laptop — Gradle itself was
# never the process that ran out.
kotlin.daemon.jvmargs=-Xmx4096m

# Run independent tasks in parallel where the module graph allows.
org.gradle.parallel=true

Expand Down
Loading