Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)
Open
Nobody has claimed this yet.
bug
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Github action workflow with default runners while building android application getting failed most of the time with below error
- What went wrong:
Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)
Runner used:
ubuntu-20.04
jvm args: -Xmx5120m -XX:MaxPermSize=4096m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
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.
Research direction
The report names a GitHub Actions workflow on ubuntu-20.04, an Android build, Gradle, and the listed JVM arguments, but no repository file or test. Start by reproducing the failure with those runner and JVM settings and inspect the workflow and runner logs; done is not defined beyond explaining or fixing the daemon disappearance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, github-actions
- Domain
- build-system, ci-cd, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100