ERROR: eslint-bridge Node.js process is unresponsive. This is most likely caused by process running out of memory

  • Versions used (SonarQube, Scanner, Plugin, and any relevant extension)
    SonarCloud
  • Error observed (wrap logs/code around triple quote ``` for proper formatting)
ERROR: eslint-bridge Node.js process is unresponsive. This is most likely caused by process running out of memory. Consider setting sonar.javascript.node.maxspace to higher value (e.g. 4096).
ERROR: Failure during analysis, Node.js command to start eslint-bridge was: {NODE_PATH=D:\a\1\s\...\Scripts\node_modules} node --max-old-space-size=4096 D:\a\1\s\.scannerwork\.sonartmp\eslint-bridge-bundle\package\bin\server 50091
  • In case of SonarCloud:
    • ALM used (GitHub, Bitbucket Cloud, Azure DevOps)
      Azure DevOps
    • CI system used (Bitbucket Cloud, Azure DevOps, Travis CI, Circle CI, Jenkins, other)
      Azure DevOps

We have TypeScript project which includes about 1300 .ts files. Sometimes analysis failes in the beginning with this error: “eslint-bridge Node.js process is unresponsive”. We tried to set different values for sonar.javascript.node.maxspace but it didn’t help. We use Azure DevOps pipelines and Microsoft hosted agents, as I know there are 7Gb of RAM.
This issue is floating, sometimes it works.
Is there any way how to fix it?

Any reply on this?

Do you see any other errors in the logs?

Could you experiment by removing dependencies in node_modules? (expect typescript)

I don’t see any other errors in the log.
After keeping only TypeScript in node_modules the process become more stable. But the error didn’t gone away completely, sometimes it still fails.

hello @aleksei.gus,

this is difficult to investigate without access to the actual project. Would it be an option for you to share the source of analyzed project with us? If possible we can arrange it privately. Another option if you want to try would be to analyze the code locally using local instance of SonarQube instead of SonarCloud.

Hi @saberduck, our repo is private but if we can share the source code privately with you it will work for us. Please let me know how I can do it.

Hi @saberduck, are you able to help my colleague Aleksei to move forward on this matter which has been blocking us for long time already?

Thanks Freddy Bang

@saberduck @Lena, I’ve shared our source code with Elena in private messages 3 weeks ago. Is there any progress on this issue? We need to fix it as soon as possible.

1 Like

About half of our scans fails today because of this issue :worried:

I have the same issue with project that reach 700+ ts files.
sonar scanner 4.3.0.2102. SonarQube server 8.2. Java 11.0.3 AdoptOpenJDK (64-bit)

But also searching for solution. In sonar-project.properties I have added

sonar.javascript.node.maxspace=8192

But this does not help.

Err header:

ERROR: eslint-bridge Node.js process is unresponsive. This is most likely caused by process running out of memory. Consider setting sonar.javascript.node.maxspace to higher value (e.g. 4096).
ERROR: Failure during analysis, Node.js command to start eslint-bridge was: {NODE_PATH=C:\repos\****\****\node_modules\@angular-devkit\build-optimizer\node_modules} node --max-old-space-size=8192 C:\repos\****\****\.scannerwork\.sonartmp\eslint-bridge-bundle\package\bin\server 63172
java.lang.IllegalStateException: eslint-bridge is unresponsive