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

SonarQube Server / Community Build
, , ,
3

Hello Dilanka
I see that you posted your issue on this older thread as well. Did you apply the recommendations shared there?
There are three of them:

  1. Set the sonar.javascript.node.maxspace analysis parameter for your scanner to increase the memory heap size for the node.js execution, as recommended in SonarQube documentation
  2. Use SonarQube 8.5 as it brings an improved analyzer for JS/TS
  3. Make sure your AzDO build agent has sufficient memory for both the scanner JVM and the Node.js heaps (e.g. if 4g and 4g make sure the agent has more than 8GB memory).

Let me know.
Best,
Sylvain

1 Like