Out Of Memory error on run SonarCloudAnalyze@3

SonarQube Server / Community Build
1

I’m trying to run code analysis:

  • Version: SonarScanner CLI 7.1.0.4889
  • The SonarQube analysis is being run from AzureDevOps Pipeline

I use tasks SonarCloudPrepare@3 and SonarCloudAnalyze@3:

- task: SonarCloudAnalyze@3
   inputs:
      jdkversion: 'JAVA_HOME_17_X64'

I get the following error on code analysis:

ERROR Error during SonarScanner Engine execution
 java.lang.OutOfMemoryError: Java heap space
	at org.sonar.api.internal.apachecommons.io.FilenameUtils.doNormalize(FilenameUtils.java:379)
 	at org.sonar.api.internal.apachecommons.io.FilenameUtils.normalize(FilenameUtils.java:1345)
	at org.sonar.api.utils.PathUtils.sanitize(PathUtils.java:42)
 	at org.sonar.api.batch.fs.internal.PathPattern$RelativePathPattern.match(PathPattern.java:102)
 	at org.sonar.api.batch.fs.internal.PathPattern$RelativePathPattern.match(PathPattern.java:97)
 	at org.sonar.scanner.scan.filesystem.AbstractExclusionFilters.isIncluded(AbstractExclusionFilters.java:118)
 	at org.sonar.scanner.scan.filesystem.FilePreprocessor.isFileIncluded(FilePreprocessor.java:121)
 	at org.sonar.scanner.scan.filesystem.FilePreprocessor.processFile(FilePreprocessor.java:63)
 	at org.sonar.scanner.scan.filesystem.ProjectFilePreprocessor.lambda$processDirectory$3(ProjectFilePreprocessor.java:170)
 	at org.sonar.scanner.scan.filesystem.ProjectFilePreprocessor$$Lambda$356/0x00007f81d838c000.execute(Unknown Source)
 	at org.sonar.scanner.scan.filesystem.DirectoryFileVisitor.visitFile(DirectoryFileVisitor.java:42)
 	at org.sonar.scanner.scan.filesystem.DirectoryFileVisitor.visitFile(DirectoryFileVisitor.java:19)
 	at java.base/java.nio.file.Files.walkFileTree(Unknown Source)
 	at org.sonar.scanner.scan.filesystem.ProjectFilePreprocessor.processDirectory(ProjectFilePreprocessor.java:169)
 	at org.sonar.scanner.scan.filesystem.ProjectFilePreprocessor.processModuleSources(ProjectFilePreprocessor.java:154)
 	at org.sonar.scanner.scan.filesystem.ProjectFilePreprocessor.processModule(ProjectFilePreprocessor.java:137)
 	at org.sonar.scanner.scan.filesystem.ProjectFilePreprocessor.processModulesRecursively(ProjectFilePreprocessor.java:125)
 	at org.sonar.scanner.scan.filesystem.ProjectFilePreprocessor.execute(ProjectFilePreprocessor.java:90)
 	at org.sonar.scanner.bootstrap.ScannerContainer.doAfterStart(ScannerContainer.java:411)
 	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:123)
 	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)
 	at org.sonar.scanner.bootstrap.GlobalContainer.doAfterStart(GlobalContainer.java:128)
 	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:123)
 	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)
 	at org.sonar.scanner.bootstrap.ScannerMain.runScannerEngine(ScannerMain.java:136)
 	at org.sonar.scanner.bootstrap.ScannerMain.run(ScannerMain.java:53)
 	at org.sonar.scanner.bootstrap.ScannerMain.main(ScannerMain.java:39)

I tried to set SONAR_SCANNER_OPTS setting by increasing memory limits and made sure that new values have applied.

variables:
      - name: SONAR_SCANNER_OPTS
        value: -Xmx12g -Xms10g

Value by default was:

INFO SONAR_SCANNER_OPTS=-Xmx8g -Xms512m -XX:+HeapDumpOnOutOfMemoryError

Now I see that new values are applied:

INFO SONAR_SCANNER_OPTS=-Xmx12g -Xms10g

But I still get the same error. I’m stucked.
Can you tell please how to fix this OOM issue?

3

Hey there.

What’s going on in the pipeline right before the OOM? Logs please. :slight_smile:

4

Sorry, here they are :slight_smile:
oom-logs.txt (13.9 KB)

5

Weird place to get an OOM error.

Can you try SONAR_SCANNER_JAVA_OPTS instead of SONAR_SCANNER_OPTS? The latter only increases memory for the JVM that spins off the real scanner (where the OOM is taking place.

6

Tried SONAR_SCANNER_JAVA_OPTS=-Xmx14g and now we get another error:

java.lang.IllegalStateException: Unable to load component class org.sonar.scanner.report.ActiveRulesPublisher

See logs
SONAR_SCANNER_JAVA_OPTS.txt (39.6 KB)

Tried change value for SONAR_SCANNER_JAVA_OPTS (both decreasing and increasing) and all pipelines are failed due to timeout.

7

Is this still the case? There was a brief incident earlier today which should have been resolved.

8

Now it’s failed due to timeout as yesterday. So, any value for setting SONAR_SCANNER_JAVA_OPTS leads to pipeline timeout.

See logs:
sonar_logs.txt (6.2 KB)

9

Thanks.

This is reminding me a bit of this thread.

Can you try setting sonar.scm.exclusions.disabled=true, and if it’s working after that, provide your .gitignore so we can try to get of the bottom of the issue?

10

I removed SONAR_SCANNER_OPTS and SONAR_SCANNER_JAVA_OPTS settings for SonarCloudAnalyze@3 task and I added sonar.scm.exclusions.disabled=true setting for SonarCloudPrepare@3 task. So I have this:

- task: SonarCloudPrepare@3
    displayName: Sonarcloud prepare
    inputs:
      SonarCloud: 'SonarCloud'
      organization: '*****'
      scannerMode: '${{ parameters.scannerMode }}'
      projectKey: '${{ parameters.projectKey }}'
      configMode: 'file'
      configFile: '${{parameters.sonarProjectBaseDir}}/sonar-project.properties'
      extraProperties: |
        sonar.scm.exclusions.disabled=true

It’s failed due to OutOfMemory error.

Judging by line
INFO Exclusions based on SCM info is disabled by configuration
logs, setting sonar.scm.exclusions.disabled has been applied. See logs here:
sonar.scm.exclusions.disabled.txt (14.7 KB)

Any other ideas?

12

Thanks for trying. I’m calling in reinforcements.

13

Hello @Rus1an ,

Please, could you run the analysis enabling the scanner debug mode? (GitHub - SonarSource/sonarqube-scan-action)
Adding -Dsonar.verbose=true, so we can get more information about the issue.

Thanks a lot.
Cheers,
Javier