-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[KSP] dagger-android hanging indefinitely on a large multi module project #4233
Comments
We can reproduce the issue, I was able to get the potential deadlock stacks (from YourKit), see here. We use Dagger 2.49 (and made the switch to ksp recently).
|
@eboudrant thanks for getting the stack traces. It looks like this is stuck on the KSP side. Do you mind filing a bug with KSP team and giving them these stack traces? |
I've attempted to switch our project using dagger-android from KAPT to KSP, but have run into issues. After manually updating all
internal
provides/binds/contributes methods to be public to address this issue: #4193, the project will hang indefinitely on thekspDebugKotlin
task in the app/root module. After updating to Kotlin 1.9.22 and KSP 1.9.22-1.0.17 which addresses the internal method issue, the same behavior occurs. It appears that the dagger KSP processor may be getting into an infinite loop somewhere. For reference, this app consists of ~300 modules.I built dagger from source to try to add some additional logging, but it looks like logs don't reach gradle output until the task ends (I manually kill it) so it makes debugging very difficult. I'm looking for some insight into where the best place to add additional debug logs would be, or if there are any hunches on where the problem might lie.
This is reproducible with both Dagger 2.49 and 2.50
The text was updated successfully, but these errors were encountered: