ConcurrentModificationException in AnalyzeProjectJob

SonarLint Eclipse
1

Using Java installation of Eclipse

Using JRE from C:\java\jdk-21.0.2+13

Starting SonarLint for Eclipse 10.2.0.81875

Analysis detected 74 issues and 0 Security Hotspots in 34747ms

Error during execution of SonarLint analysis

java.util.ConcurrentModificationException

at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1714)

at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)

at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)

at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921)

at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)

at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682)

at org.sonarlint.eclipse.core.internal.jobs.AnalyzeProjectJob.trackIssues(AnalyzeProjectJob.java:345)

at org.sonarlint.eclipse.core.internal.jobs.AnalyzeProjectJob.lambda$20(AnalyzeProjectJob.java:313)

at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2451)

at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2471)

at org.sonarlint.eclipse.core.internal.jobs.AnalyzeProjectJob.updateMarkers(AnalyzeProjectJob.java:313)

at org.sonarlint.eclipse.core.internal.jobs.AnalyzeProjectJob.runAnalysisAndUpdateMarkers(AnalyzeProjectJob.java:251)

at org.sonarlint.eclipse.core.internal.jobs.AnalyzeProjectJob.doRun(AnalyzeProjectJob.java:182)

at org.sonarlint.eclipse.core.internal.jobs.AbstractSonarJob.run(AbstractSonarJob.java:37)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
3

Hey @jukzi,

thanks for reaching out and sorry for the late response.
We are currently working on the analysis logic in SonarLint. With the next release, it will be gone, including the exception you have; sorry for the inconvenience.
The next release is planned to be done in two weeks.

If you want, you can already try our dogfooding builds to see that the error is gone.

Best,
Tobias