Template for a good new topic, formatted with Markdown:
ALM used - Azure DevOps
CI system used - Azure DevOps
Error observed:
INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 8:54.717s
INFO: Final Memory: 1059M/3548M
INFO: ------------------------------------------------------------------------
##[error]ERROR: Error during SonarScanner execution
ERROR: Error during SonarScanner execution
##[error]java.lang.StackOverflowError
java.lang.StackOverflowError
##[error]at java.base/java.util.HashMap.hash(HashMap.java:338)
at java.base/java.util.HashMap.getNode(HashMap.java:568)
at java.base/java.util.HashMap.containsKey(HashMap.java:594)
at java.base/java.util.HashMap.hash(HashMap.java:338)
at java.base/java.util.HashMap.getNode(HashMap.java:568)
at java.base/java.util.HashMap.containsKey(HashMap.java:594)
##[error]at com.sonar.security.G.B.A(na:258)
at com.sonar.security.G.B.A(na:3320)
at com.sonar.security.G.B.A(na:3320)
at com.sonar.security.G.B.A(na:3320)
at com.sonar.security.G.B.A(na:3320)
at com.sonar.security.G.B.A(na:3320)
at com.sonar.security.G.B.A(na:3320)
at com.sonar.security.G.B.A(na:3320)
Above error shows in the Run Code analysis task in azdo pipeline.
This definitely seems like a bug and I would be happy to fix it.
Interestingly, it occurs in a very old part and “well-proven” part of the code, so it is rather surprising to me.
In order to help me help you, could you send me a zip file of the ucfg2 dir inside the .scannerwork directory generated during analysis? According to your logs, it was at the location C:\a\6\s\.scannerwork\ucfg2\ when you ran the analysis. You can send it to me as a private message so that you do not have to share it publicly in this thread.
Thank you, @rahul.shankhareman ! I confirm reception of the files. I created an internal ticket and I plan to look into it this week. I will hopefully have some news for you by the end of the week.
I am happy to confirm that we identified and fixed this issue. It will be released today and deployed on SonarCloud this week. You should see this error disappear within the next few days.