SonarQube - Developer Edition Version 8.7 (build 41497)
Scanner - sonar-maven-plugin Version 3.7.0.1746
Project codebase - Java v1.8
Error during scanning
[ERROR] GC overhead limit exceeded → [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following articles: OutOfMemoryError - Apache Maven - Apache Software Foundation
Greetings @nikolay.sidorenko
thanks for reaching out to us with this report.
In order to troubleshoot SonarQube analysis, verbose logs are needed.
Could you please run this analysis again with DEBUG log level enabled? And please make sure to capture both stdin and stderr with your log capture.
A few additional information which may be useful as well:
did you analyze this project successfully on SonarQube before, maybe on some older SonarQube or with the Community Edition?
any reason for you to stay on version 8.7? SonarQube 8.9 provides 119 improvements and bug fixes for the Java analyzer only
Java 11 is known to better manage memory consumption than Java 8, would it be possibile for you to test an analysis using Java 11?
Thanks for this good news @nikolay.sidorenko
With your previous logs, S5145 was indeed a good candidate as the analysis stopped there.
I am not surprised that analysis memory consumption increased a lot with your upgrade to the Developer Edition. Taint Analysis and the related security rules are not part of the Community Edition, and they are much more memory intensive than the Java analysis Open Source part.
We are also aware that on some large projects this scanner memory usage can become a problem, your analysis DEBUG logs may help us further with our effort to limit this memory consumption.