which versions are you using SonarQube Server 2026.1 LTA, Scanner: sonar-maven-plugin:jar:4.0.0.412
how is SonarQube deployed: zip
what are you trying to achieve: scanning the same project after upgrade the server from 2025.1 LTA to 2026.1 LTA
what have you tried so far to achieve this: doubling the heap size
Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!
After upgrading from SonarQube 2025.1 LTA to 2026.1 LTA, our Maven scanner (mvn sonar:sonar) heap requirement increased from “-Xmx12G” to “-Xmx24G” for the same project. Is a doubling of required heap size expected?
Normally, as new rules are introduced and existing rules are improved, analyses might require more memory. However, a 12 GB increase sounds really steep, even for an update between 2 versions that are 1 year apart.
It would be interesting to know what is the analysis doing when the OOM happens. You could set the heap size to the same value that was before and turn on debug-level analysis logging (-X on Maven). What sensor/analyzer was running when the OOM happened? It would also be interesting to compare these logs with pre-upgrade debug logs.
Also: is your quality profile Sonar Way (or one that extends it)? If so, then new rules added to it by the upgrade might be the cause. If you have a backup of your pre-upgrade DB, you could try spinning it up, exporting the quality profile, loading it into the new instance and analyzing the project with it, just to compare.
A few extra notes, likely unrelated to your issue, but that you should consider:
You’re using a 2-year-old version of the scanner for Maven (see release history).