Gradle starts a new daemon every build and says others could not be reused
Starting a Gradle Daemon, 1 busy and 6 stopped Daemons could not be reused, use --status for detailsShort answer
This line is a notice, not a failure. Gradle reuses only a daemon that is idle and matches the build: same Gradle version, same Java and same JVM arguments. A busy one is mid-build; stopped ones were shut down. Run gradle --status, stop old daemons with gradle --stop and keep JVM settings identical across tools.
Fix it fast
1Find out which cause you have
List the daemons Gradle knows about. The status column shows which are busy, idle or stopped, and which Gradle version each one runs.
./gradlew --status2Match what you see, then jump to its fix
- 1
--status lists a daemon as BUSY while you start a second buildAnother build is still using the daemonFix - 2
Every tool you switch between starts a new daemon, and the old ones stay idleThe IDE, the terminal and the wrapper use different JVM settingsFix - 3
--status shows several STOPPED entries and no idle oneDaemons were stopped for low memory or idle timeFix
- 1
What does the error look like?
Starting a Gradle Daemon, 1 busy and 6 stopped Daemons could not be reused, use --status for details
Cause 1 of 3
Another build is still using the daemon
1Check
A busy daemon is already running a build, so it cannot take another one. This happens when the IDE syncs while a terminal build runs, or when two terminals build at once.
./gradlew --status2Fix
Let the first build finish, or cancel it. Gradle then starts a second daemon on its own for the new build, which is normal. If a build is stuck, stop the daemons of this Gradle version.
./gradlew --stop3Verify
The status list shows no BUSY entry left over.
./gradlew --statusConfirmed by docs.gradle.org
Cause 2 of 3
The IDE, the terminal and the wrapper use different JVM settings
1Check
A daemon is compatible only on exact matches: Gradle version, Java version, and immutable JVM arguments such as -Xmx and -Xms. Changing org.gradle.jvmargs or GRADLE_OPTS in one place makes a new daemon.
grep -n "jvmargs" gradle.properties ~/.gradle/gradle.properties
echo "$GRADLE_OPTS"
./gradlew --version2Fix
Set org.gradle.jvmargs once in gradle.properties and remove conflicting values elsewhere. Point the IDE's Gradle JDK at the same JDK as the terminal.
# gradle.properties
org.gradle.jvmargs=-Xmx2g3Verify
Build once from the terminal and once from the IDE, then count the daemons.
./gradlew --statusConfirmed by docs.gradle.org
Cause 3 of 3
Daemons were stopped for low memory or idle time
1Check
A daemon stops when you run --stop, when available system memory is low, or after 3 hours idle, so the next build starts a fresh one.
./gradlew --status2Fix
Nothing is broken. If memory is tight, lower the heap in org.gradle.jvmargs and close other heavy programs. Use --no-daemon only for one-off builds, such as a short CI job.
./gradlew assembleDebug --no-daemon3Verify
The build finishes and the notice disappears once an idle compatible daemon exists.
./gradlew --statusConfirmed by docs.gradle.org
How do I stop it coming back?
- Keep org.gradle.jvmargs in one gradle.properties file and do not export GRADLE_OPTS differently in each shell.
- Use the same JDK in the IDE and in the terminal.
- Run gradlew --stop after upgrading Gradle or the JDK, so old daemons do not pile up.
- Avoid starting a terminal build while the IDE is still syncing.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
The Gradle daemon dies in the middle of a Jenkins or CI build
Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)
The process that runs your build vanished before it reported back.
2 causes, each with a fixMobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
The phone shows as unauthorized and Android Studio will not run the app
adb devices lists the phone but Android Studio cannot deploy to it
An unauthorized phone means it has not trusted this computer's RSA key.
3 causes, each with a fixMobile apps
Android Studio cannot pair the phone over Wi-Fi
The Pair devices over Wi-Fi dialog lists no device
Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.
4 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fix