# Gradle build stuck on configuring for 14 hours

**URL:** <https://discuss.gradle.org/t/gradle-build-stuck-on-configuring-for-14-hours/36525>\
**Category:** Help/Discuss\
**Created:** [June 16, 2020, 7:13pm UTC](https://discuss.gradle.org/t/gradle-build-stuck-on-configuring-for-14-hours/36525 "2020-06-16T19:13:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![samtstern](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@samtstern](https://discuss.gradle.org/u/samtstern)\
**Post date:** [June 16, 2020, 7:13pm UTC](https://discuss.gradle.org/t/gradle-build-stuck-on-configuring-for-14-hours/36525/1 "2020-06-16T19:13:26Z")

</div>

I am just trying to run `./gradlew clean` and my build hangs forever while repeatedly spitting out the same debug logs:

```gradle
15:12:18.482 [DEBUG] [org.gradle.launcher.daemon.server.health.LowMemoryDaemonExpirationStrategy] Received memory status update: {Total: 17179869184, Free: 7033536512}
15:12:18.483 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting JVM memory status event {Maximum: 7635730432, Committed: 468189184}
15:12:23.484 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting OS memory status event {Total: 17179869184, Free: 7022985216}
15:12:23.485 [DEBUG] [org.gradle.launcher.daemon.server.health.LowMemoryDaemonExpirationStrategy] Received memory status update: {Total: 17179869184, Free: 7022985216}
15:12:23.486 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting JVM memory status event {Maximum: 7635730432, Committed: 468189184}
15:12:23.961 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
15:12:23.961 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
15:12:23.962 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
15:12:23.962 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
15:12:23.963 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
15:12:23.963 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
15:12:23.963 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
15:12:28.483 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting OS memory status event {Total: 17179869184, Free: 6689746944}
15:12:28.484 [DEBUG] [org.gradle.launcher.daemon.server.health.LowMemoryDaemonExpirationStrategy] Received memory status update: {Total: 17179869184, Free: 6689746944}
15:12:28.484 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting JVM memory status event {Maximum: 7635730432, Committed: 468189184}
15:12:33.481 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting OS memory status event {Total: 17179869184, Free: 6436581376}
15:12:33.482 [DEBUG] [org.gradle.launcher.daemon.server.health.LowMemoryDaemonExpirationStrategy] Received memory status update: {Total: 17179869184, Free: 6436581376}
15:12:33.482 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting JVM memory status event {Maximum: 7635730432, Committed: 468189184}
15:12:33.963 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
15:12:33.964 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
15:12:33.964 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
15:12:33.964 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
15:12:33.965 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
15:12:33.965 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
15:12:33.965 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
15:12:38.482 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting OS memory status event {Total: 17179869184, Free: 6753517568}
15:12:38.482 [DEBUG] [org.gradle.launcher.daemon.server.health.LowMemoryDaemonExpirationStrategy] Received memory status update: {Total: 17179869184, Free: 6753517568}
15:12:38.483 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting JVM memory status event {Maximum: 7635730432, Committed: 468189184}
<-------------> 0% CONFIGURING [6m 56s]

```

I have waited over 25 minutes, no change. I have also:

- Restarted my computer
- Used the nuclear option here: [https://github.com/rock3r/deep-clean](https://github.com/rock3r/deep-clean)

I just can’t get it to do anything.

---

<div class="post-metadata">

**Author:** ![samtstern](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@samtstern](https://discuss.gradle.org/u/samtstern)\
**Post date:** [June 16, 2020, 8:32pm UTC](https://discuss.gradle.org/t/gradle-build-stuck-on-configuring-for-14-hours/36525/2 "2020-06-16T20:32:49Z")

</div>

I tried these solutions but to no avail:

- [Gradle performance issues](https://discuss.gradle.org/t/gradle-performance-issues/23057/4)
- [Root project configuration takes too long on Mac](https://discuss.gradle.org/t/root-project-configuration-takes-too-long-on-mac/21653/2)
- [https://stackoverflow.com/questions/33289695/inetaddress-getlocalhost-slow-to-run-30-seconds/33289897#33289897](https://stackoverflow.com/questions/33289695/inetaddress-getlocalhost-slow-to-run-30-seconds/33289897#33289897)

I also tried upgrading my Java version from Java 8 to Java 11. Same result.

---

<div class="post-metadata">

**Author:** ![samtstern](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@samtstern](https://discuss.gradle.org/u/samtstern)\
**Post date:** [June 17, 2020, 12:16pm UTC](https://discuss.gradle.org/t/gradle-build-stuck-on-configuring-for-14-hours/36525/3 "2020-06-17T12:16:21Z")

</div>

I think this is some kind of record:

 ![Screen Shot 2020-06-17 at 8.15.07 AM](https://global.discourse-cdn.com/gradle/original/2X/e/e24f638f4bc5fdef7028852f5b468c8c3e943415.png)

---

<div class="post-metadata">

**Author:** ![sterling](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/sterling/32/5395_2.png) [@sterling](https://discuss.gradle.org/u/sterling)\
**Post date:** [June 18, 2020, 9:55pm UTC](https://discuss.gradle.org/t/gradle-build-stuck-on-configuring-for-14-hours/36525/4 "2020-06-18T21:55:17Z")

</div>

Those log messages are normal and periodic. They would come out regardless of the hang.

It’s likely that you’re hitting some kind of concurrency bug. Which version of Gradle is this?

Could you get a [thread dump](https://www.baeldung.com/java-thread-dump) from the daemon when this happens? You need to grab this from the process running the “GradleDaemon” class (find the pid by running jps).

---

<div class="post-metadata">

**Author:** ![samtstern](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@samtstern](https://discuss.gradle.org/u/samtstern)\
**Post date:** [June 19, 2020, 1:04pm UTC](https://discuss.gradle.org/t/gradle-build-stuck-on-configuring-for-14-hours/36525/5 "2020-06-19T13:04:06Z")

</div>

Sure, here’s the thread dump:  
[https://pastebin.com/VJ0WjFFE](https://pastebin.com/VJ0WjFFE)

Oh and it was gradle 5.4.1
