The analysis will stop due to the Node.js process running out of memory - getting this error in Azur

SonarQube Server / Community Build
1

Have installed SonarQube Community edition in a Azure windows VM and running the analysis.
##[error]ERROR: The analysis will stop due to the Node.js process running out of memory (heap size limit 2096 MB)
##[error]ERROR: You can see how Node.js heap usage evolves during analysis with “sonar.javascript.node.debugMemory=true”
##[error]ERROR: Error during SonarScanner execution

##[debug]Processed: ##vso[task.logissue type=error;]ERROR: Error during SonarScanner execution

ERROR: Error during SonarScanner execution

INFO: ------------------------------------------------------------------------

##[error]java.lang.IllegalStateException: Analysis of JS/TS files failed

##[debug]Processed: ##vso[task.logissue type=error;]java.lang.IllegalStateException: Analysis of JS/TS files failed

java.lang.IllegalStateException: Analysis of JS/TS files failed

##[error]at org.sonar.plugins.javascript.analysis.AbstractBridgeSensor.execute(AbstractBridgeSensor.java:96)

2

Hey there.

Have you checked the docs?

Consider the property setting sonar.javascript.node.maxspace to a higher value depending on the host’s available memory.

3

Hi Colin,
Thanks for the input. The issue is solved after me giving the maxspace value in varaibles of pipeline. But now I am facing one more issue.
##[error]OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000577800000, 721420288, 0) failed; error=‘The paging file is too small for this operation to complete’ (DOS error/errno=1455)
I have increased the paging size in the VM but still this issue occurs. Do I have to give this is variables of the pipeline as well? If Yes whats the Key and Value that I can give?

4

It’s not clear to me what’s going on in the scan when you receive this error. Please share what’s going on in the logs beforehand :slight_smile: