-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Question / Bug] dependencyCheckAggregate task is stuck #6852
Comments
You might be stuck in a garbage collection loop due to low memory in Gradle Daemons perhaps? You could look at memory/cpunusage and see if it's stuck (doing nothing) or stuck (doing something). As a side note, do you happen to have JavaScript dependencies in your projects? |
Memory usage doesn't change. CPU doesn't change. I did a thread dump now after getting stuck using jstack on both involved java processes (started from command line, I'm running Windows 11 by the way):
Maybe these are helpful to someone. gradle-properties:
|
Looks like a deadlock of some sort to me. Worker threads are waiting for a lock held by The thread that has the lock that everything else is waiting on is at Could also be to do with issues with Gradle and/or the Gradle plugins you are using along with parallel execution more than anything within OWASP Dependency check (but I don't really know). All I can suggest is
|
Thanks for the suggestions. I'll update this reply with new information as I collect it:
This does not seem to help. I've even tried with an empty list but it still gets stuck
I've tried this but it doesn't work (neither Windows nor MacOS), see findings below.
I'm not sure exactly what this means, but I am guessing that it is not feasible for my project where parallelism is a must to reduce build time
I am running Gradle 8.7 due to google/play-services-plugins#299 but I am pretty certain that I had the same issue when I was briefly on 8.8/8.9 before reverting
I'm not sure exactly what this means
This is a problem both on Windows and MacOS (M1) at least Interesting finding 1
I still get stuck on
Interesting finding 2
The number never changes, but I can see the same log message several times in quick succession Interesting finding 3
After this execution does not terminate but there is no more log output Interesting finding 4 |
Api request failures have nothing to do with deadlocks. Plenty of other tickets and guidance on this one. |
Sure, but that is just a small finding while I attempted to troubleshoot. I have other projects where the plugin works well with the same setup (difference in dependencies and modular structure of course) |
Problem: My Gradle project times out (1 hour execution time) whereas some of my other Gradle projects, with same/similar setup, execute within 5 minutes or so. There's no obvious difference in configuration.
The build is stuck in this phase in one of the projects:
What could I do to troubleshoot this? I don't think changing the timeout will help as I've run without timeout and waited 2 hours and counting...
Top level declaration (Gradle Kotlin DSL):
The task that I run:
(I've also tried with --stacktrace but with no additional information...)
My setup:
Possibly related: #3897
The text was updated successfully, but these errors were encountered: