Build stuck on kspDebugKotlin when using KSP on large project (dagger ksp) 8000 #1720
Assignees
Comments
|
I experience similar issue. There are 125 modules in the project. YourKit points to a potential deadlock in this thread with comment: "It seems that the following threads have not changed their stack for more than 10 seconds". Potential deadlock threadsThe stacktrace doesn't mention any ksp work, but this problem happens only when ksp is enabled in the project. Is there any other data that would be helpful? Unfortunately, I can't share the project as it's closed-source. |
|
When I run build with Gradle logs ( Logs repeatedly printed to the console |
|
I experienced the same and it turned out there is a freezed Kotlin deamon process. I killed the process and get unstuck. So the problem is probably not ksp but Kotlin daemon. |
|
We also just started seeing this problem for our local developers. We only started having it when updating from |
|
We kept having people encounter this issue and waste a lot of time on it, so in our build I have added something to try to auto detect and fix the issue to mitigate it for now. I added a timeout setting on the KSP task And then in a build listener I check for the ksp timeout and can kill the kotlin daemon and print an error message explaining what happened |
|
+1 to this being a kotlin daemon issue. I wrote the original dagger issue linked to this issue. I last tried this with kotlin I then used the gradle-profiler to compare dagger-android KSP vs KAPT build times and ran into some extremely long incremental build times where the underlying issue seems to be in the Kotlin daemon. Warm daemonWhen I ran using a warm daemon, I had a couple incremental builds reach 25 minutes. Here's a screengrab from Develocity showing one of those builds where almost all the time was in the root module's ksp task. Here's the raw output and build times before I killed the run. Cold daemonI then ran the exact same scenario with the |
|
KSP 2.0.20-1.0.25 is just released and may have fixed this issue. Would you mind to give it a try? |
|
I am also facing the same issue but in my case it never completes ksp - 2.1.21-2.0.1 ksp.useKSP2=true Edit: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We recently moved to ksp from kapt for dagger and we're facing some build getting stuck. Gradle is stuck on
kspDebugKotlinon random module using dagger ksp.We're using :
We have ~300 modules.
I was able to get some thread stacks using YourKit :
I can't really confirm but it seems it only happen when I have Android Studio open.
Originally reported here : google/dagger#4233
The text was updated successfully, but these errors were encountered: