You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Optional) Kotlin and Kotlin Gradle Plugin (KGP) version
1.9.23
(Optional) Android Gradle Plugin (AGP) version
8.3.2
Describe the bug
The task computeActualUsageDebug gets stuck for a long time.
This module contains only android resources(images, vector drawables, translations and theme definitions), no code, so I don't understand why it takes so long. It has around 250 files on it and it takes around 5-10 min to run in a M1 machine doing no other heavy compilation.
The same task in other big modules with lots of code and dependencies takes way less time. I checked the memory usage in the gradle daemon and it seemed fine (not a lot of GCs happening).
Is there any debug flag I could pass to the build that could give me infos about what is happening?
Expected behavior
To run the analysis faster?
Additional context
My gradle.properties has, if I remove this flag, computeActualUsageRelease also gets stuck.
dependency.analysis.android.ignored.variants=release
The text was updated successfully, but these errors were encountered:
Thanks for the issue. My first thought was memory, and it still might be the case. Do you have a build scan you can share?
You could use gradle-profiler to profile the build for CPU and memory usage and see what seems to be taking so long. I would run just the task in question to keep the profile useful. I'm happy to take a look if you're willing to share the reports. I have done so in the past.
Build scan link
Plugin version
1.31.0
Gradle version
8.6
JDK version
21.0.2 (BellSoft 21.0.2+14-LTS)
(Optional) Kotlin and Kotlin Gradle Plugin (KGP) version
1.9.23
(Optional) Android Gradle Plugin (AGP) version
8.3.2
Describe the bug
The task
computeActualUsageDebug
gets stuck for a long time.This module contains only android resources(images, vector drawables, translations and theme definitions), no code, so I don't understand why it takes so long. It has around 250 files on it and it takes around 5-10 min to run in a M1 machine doing no other heavy compilation.
The same task in other big modules with lots of code and dependencies takes way less time. I checked the memory usage in the gradle daemon and it seemed fine (not a lot of GCs happening).
Is there any debug flag I could pass to the build that could give me infos about what is happening?
Expected behavior
To run the analysis faster?
Additional context
My
gradle.properties
has, if I remove this flag,computeActualUsageRelease
also gets stuck.dependency.analysis.android.ignored.variants=release
The text was updated successfully, but these errors were encountered: