Forked daemons don't removed after a build finishes

[denzap]

Here is the setup when forked daemons produced by napt aren't being removed after build finishes:

gradle = 8.4
kotlin = 1.9.0
agp = 8.1.2
java = 17
dagger = 2.48.1

You can apply patch to main branch broken_forked_daemon.patch and run
./gradlew :sample-android-app:assembleDebug --no-build-cache --no-configuration-cache --rerun-tasks
and see that forked daemons are still alive after build finishes.

This is not reproduced on main branch, but it has pretty old setup of environment

This is a unexpected behaviour, because of non optimal memory usage, especially in multimodal project with a big number of workers

[denzap]

It appeared to be a new gradle 8.3 feature https://docs.gradle.org/8.3/release-notes.html#faster-java-compilation

As workaround you can use systemProp.org.gradle.internal.java.compile.daemon.keepAlive=SESSION in your gradle.properties or do nothing)