has anyone had issues with multiple daemons spinni...
# performance
a
has anyone had issues with multiple daemons spinning up out of nowhere? I mean im not building in the IDE, essentially,
Copy code
./gradlew --stop
No Gradle daemons are running.
./gradlew --stop
Stopping Daemon(s)
2 Daemons stopped
nonstop. killing java process resuscitates the daemons. these extra "zombie" daemons do not persist on next run, and force more daemons to run.
noticed on both gradle 8.11.1 and 8.12
then strangely im getting:
Copy code
Calculating task graph as configuration cache cannot be reused because an input to task ':buildSrc:compileJava' has changed.
even though nothing actually changed
tracing the logs it seems like there is something Intellij is doing, its constantly configuring gradle in the background based on the logs of the daemon
it wants to use the default JBR java home, and ignoring my new java location in
$JAVA_USER_HOME
looks like intellij ultimate is doing it, but not Android studio
t
I've seen similar in some builds of studio. IIRC it was a nightly of 2025.1 it would just decide to rerun whatever the last run config was after seemingly arbitrary actions in the IDE. Would have to kill the IDE to get it to stop for a bit.
a
Yeah I noticed killing the ide kills the zombie daemon. It really eats into machine performance 😥
💯 1
t
hmm Interesting. We don't use apollo but perhaps something else in our build has a similar issue
m
Hey @Andrew Grosner I've reported that issue, there's just been a new release, please give a try! Also, any chance you're using Jetbrains Toolbox?