Skip to content
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

Stuck in computeActualUsageDebug for many minutes #1186

Open
juliocbcotta opened this issue May 8, 2024 · 1 comment
Open

Stuck in computeActualUsageDebug for many minutes #1186

juliocbcotta opened this issue May 8, 2024 · 1 comment

Comments

@juliocbcotta
Copy link

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

@autonomousapps
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants