Gradle Daemon stuck at IDLE and never ends on Windows

Help/Discuss
1

It used to be fine days ago. Now it sticks like this:

PS C:\Users\Lau\IdeaProjects\something> ./gradlew runClient        
Starting a Gradle Daemon, 2 incompatible and 5 stopped Daemons could not be reused, use --status for details

> IDLE

The task does execute, anyway. It just has no output, and would not exit after finishing the task.
When I checked into daemon log, I saw INFINITE LOOP of this at the end:

2025-07-31T12:07:47.699+0800 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
2025-07-31T12:07:47.699+0800 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
2025-07-31T12:07:57.698+0800 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.

And about one hundred lines of “Is this a loopback interface?” at the start. I don’t know if it’s normal, because I’ve never read or learned about Gradle Daemon logs. :frowning:
I don’t think it’s Gradle version stuff, since I’ve not changed anything in my code and it used to work. All of my Android projects and Minecraft projects are broken like this (which means all my Gradle projects). I’ve tried deleting the whole gradle user home, upgrading my JDK and the problem just didn’t fix up.
The output of ./gradlew --version:

Gradle 8.12.1
------------------------------------------------------------

Build time:    2025-01-24 12:55:12 UTC
Revision:      0b1ee1ff81d1f4a26574ff4a362ac9180852b140

Kotlin:        2.0.21
Groovy:        3.0.22
Ant:           Apache Ant(TM) version 1.10.15 compiled on August 25 2024
Launcher JVM:  21.0.8 (Azul Systems, Inc. 21.0.8+9-LTS)
Daemon JVM:    C:\Program Files\Zulu\zulu-21 (no JDK specified, using current Java home)
OS:            Windows 11 10.0 amd64

By the way, I upgraded my Windows from 23H2 to 24H2 and installed a new SSD as the system partition disk this week. I don’t know if any of these caused the problem.

2

Those logs in the daemon are normal, they just show that the daemon is still running as expected, doing regular maintenance work.

Maybe --info or --debug reveal more of what is going on when it is or seems to hang.

3

Thanks for your reply.:smiling_face_with_three_hearts: I’m tired of all the issues I’m having with 24H2 so I just rolled back to 23H2. And everything is just back to work.:joy:So I’m pretty sure it’s certain issue with 24H2 updates.
I’ve tried to use --debug and --info following the steps I found on Google but I didn’t save the output. I remember it didn’t have anything that look strange in the output, said something like “(build should start)” and started hang.
However, it’s not actually “hanging” because the Minecraft client did pop up after a period of time, which looks like the build is done like normal, but just the communication between gradle and daemon has been cut down (by Windows?), so there is no output to CLI. IDEA Run and Debug didn’t work either.

4

I checked my Windows Update Log and it says that I’m on 24H2 since months without problems. :man_shrugging:

5

I have no idea about what happened to my PC.:joy: Maybe some new system settings or firewall stuff but I don’t know how to fix them.
Anyway, thank you for help.:smiling_face_with_three_hearts: I may re-upgrade to 24H2 in the future and I promise I’ll come back here if things are still wrong.

1 Like