Gradle Kotlin daemon infinite loop until JVM max memory runs out
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, docker, gitlab, kotlin, react-native
- Domain
- build-system, ci-cd, devops
Research direction
Start with the linked job.log and the GitLab CI/CD pipeline environment for the react-nativecommunity/react-native-android image. Focus on the ./gradlew bundleRelease entry point and the :react-native-gradle-plugin:compileKotlin task, comparing runs with and without diagnostic options. Done means identifying a reproducible cause or a concrete fix for the Kotlin daemon loop and memory exhaustion.
Written by the indexing model from the issue text.
Description
Hello, thank you react native community for supporting this Docker image!
Issue Environment:
- Runtime:
GitLab CI/CD Pipeline Job - Image:
reactnativecommunity/react-native-android:latest(also tried6.0and5.4) - Gradle:
7.5.1 - Android SDK Level:
31 - jvmargs:
-Xmx16g -Xms2g \ -XX\:MetaspaceSize\=512m -XX\:MaxMetaspaceSize\=1g \ -XX\:NewSize\=256m -XX\:MaxNewSize\=3g \ -Dfile.encoding\=UTF-8 - Dependencies:
node_modulesis downloaded from previous job which contains the necessary react native modules
Issue Description:
When attempting to run ./gradlew bundleRelease the Gradle daemon starts as expected but on the first task :react-native-gradle-plugin:compileKotlin causes an infinite loop with the Gradle kotlin daemon. When running with no options, the daemon runs out of memory (15.7GiB) and closes at about 15 minutes of running. With info or debug/stacktrace option, daemon runs out of memory and closes at about 45 minutes of running.
Issue Reproduction:
I cannot reproduce this issue locally, only in the pipeline pod which uses this Docker image. Please look through the debug/stacktrace log dump below.
Issue Logs:
job.log
I am grateful for any expert to provide a diagnosis on what could be causing this!
- Dominant language
- Dockerfile
- Stars
- 541
- Forks
- 152
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from react-native-community/docker-android
-
Difficulty 1/5 1-3 hours Newbie friendliness 70/100
react-native-community/docker-android#250 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
react-native-community/docker-android#219 · 5 comments · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
react-native-community/docker-android#215 · 5 comments · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
react-native-community/docker-android#166 · 12 comments · 13 reactions ·
All issues in react-native-community/docker-android
Similar issues
-
Needs Design Priority: Wishlist
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
elementary/flatpak-platform#253 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/hone-maven-plugin#1060 ·
-
0.kind: build failure
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Update Vish to 1.1.5 Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100