-
Notifications
You must be signed in to change notification settings - Fork 136
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
Findbugs hangs for a long time without producing logs and then exits with EmptyStackException error #367
Comments
Update: the last pipeline I ran just hung until the timeout of 8 hours, after that it produced these errors:
Could this be the cause? |
Hello, have you found a solution ? it seeems I have a similar problem with sonarqube scanner on jenkins since I upgraded from sonar 7.9 to 8.9 LTS.
|
Hello christopheroger,
I found a workaround by executing the scan in -X mode (debug) and forcing the execution of the scanner using one thread (it is not thread safe). By doing that, I was able to identify the java and class file that was causing the script to fail (it was stuck for an entire hour at that file). Basically what was happening was that the java file would explode the graph creation. I think that it was a memory error, 3 GB of heap didn't help.
|
Issue Description
Hi, I'm having a issue with Findbugs: it has been a while since I ran the last sonar analysis using findbugs (on March 2021). The last time I used the plugin would elapse 20 minutes to produce the report to be sent to Sonarqube. I'm using the maven plugin for sonar-scanner and nothing has changed since then except the code to review. The main issue is that this is a multi-module project with cascade-style dependencies (the module after depends on the previous one) with millions lines of code. In particular, findbugs hangs on one of the biggest modules for more than a hour (sometimes even 5 hours)
It then interrupts the execution with an error, here there is the complete StackTrace that maven gave me using the -e switch:
Before this error occurred, I stumbled across two errors, one given by the fact that there wasn't enough Java Heap space, one regarding the TimeoutException (extended the timeout to an unrealistic time, 6 hours)
I already have JVM heap memory expanded to min 500 MB and max 2048 MB and tried to play with Findbugs settings on the Sonarqube server, using minimal effort to find bugs and so on.
The issue seems related to the size of the module which contains a lot of dependencies and several java files, 1929.
The maven command I use to issue the analysis is the following:
Have you ever stumbled upon a scenario like that?
The text was updated successfully, but these errors were encountered: