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)