Thank you for your report. We deployed a new version of the analyzer that is failing for you (according to your logs) on SonarCloud at the end of February. This new version specifically addresses some performance and memory issues that we observed in the context of JS/TS. Can you confirm that you are still seeing the same problem as of today?
First thing I would like to explore whether there is an infinite recursion somewhere or just a deep one that is exceeding the standard stack size.
To test this, could you try to run the analysis with a huge stack size? For this you would need to set the environment variable SONAR_SCANNER_OPTS="-Xss10m" when running the scanner command.
Now that we confirmed that something is not behaving as expected, it would be super useful if you could provide the content of the /home/vsts/work/1/s/.scannerwork/ucfg2/js folder. It will enable us to understand exactly what is happening and be sure we find an appropriate solution.
Please do not post them here, I will reach out to you privately.
Hi Quentin, it seems that Arno has sent you the requested JavaScript folder contents via email. Have you had the opportunity to review and analyze them?
We had the opportunity to review them, and we managed to reproduce the error.
We had a look from different points of view, unfortunately, it was not enough to understand exactly what is happening.
We still keep this task in our backlog, we will keep you posted as soon as we have a better understanding of what is happening.