Starting a Gradle Daemon, 1 busy and 6 stopped Daemons could not be reused, use --status for details

Question

When I was running the gradle clean command, I got the following message

Starting a Gradle Daemon, 1 busy and 6 stopped Daemons could not

Answer 1

Just add two lines in your gradle properties:

org.gradle.daemon=true

org.gradle.parallel=true

Answer 2

Stopping an existing Daemon:

If you want to explicitly stop running Daemon processes for any reason, just use the command gradle --stop.

Note: for your consideration the gradle --stop command won’t stop daemons running with a different version of Gradle.

How to kill all Daemon process on my machine?

Gradle will kill any Daemon that has been idle for 3 hours or more, so you don’t have to worry about cleaning them up manually.

Resource Link: Gradle Daemon Issue Details

So the command and output are given below:

$ gradle --stop
Stopping Daemon(s)
2 Daemons stopped

After stopping daemons, status will be look like below:

$ gradle --status
No Gradle daemons are running.
   PID STATUS   INFO
  8027 STOPPED  (stop command received)
  9347 STOPPED  (stop command received)
 12448 STOPPED  (stop command received)
 11506 STOPPED  (stop command received)
 11727 STOPPED  (by user or operating system)
  4786 STOPPED  (by user or operating system)
 14569 STOPPED  (by user or operating system)
 31237 STOPPED  (by user or operating system)

If you are stuck with gradle build running, you can to through this post: Stuck with Gradle Build Running

Answer 3

I solve it with another method in other post. By removing folders like 4.4 4.6 5.4.1 5.5 in directory as below

/users/[username]/.gradle/daemon

java.lang.OutOfMemoryError: GC overhead limit exceeded