NPE in SonarLint for IntelliJ

SonarLint IntelliJ Platform
,
1

Environment:

  • Java: JetBrains s.r.o. 11.0.15
  • OS: Windows 11 amd64
  • IDE: IntelliJ IDEA 2022.1.2
  • SonarLint: 6.7.0.45926
java.lang.RuntimeException: java.lang.NullPointerException
	at c.ij.oa.application.impl.LaterInvocator.invokeAndWait(LaterInvocator.java:119)
	at c.ij.oa.application.impl.ApplicationImpl.invokeAndWait(ApplicationImpl.java:503)
	at c.ij.oa.application.impl.ApplicationImpl.invokeAndWait(ApplicationImpl.java:523)
	at c.ij.oa.project.impl.ProjectManagerExImplKt.openProject(ProjectManagerExImpl.kt:591)
	at c.ij.oa.project.impl.ProjectManagerExImplKt.access$openProject(ProjectManagerExImpl.kt:1)
	at c.ij.oa.project.impl.ProjectManagerExImpl$doOpenAsync$1.invoke(ProjectManagerExImpl.kt:145)
	at c.ij.oa.project.impl.ProjectManagerExImpl$doOpenAsync$1.invoke(ProjectManagerExImpl.kt:56)
	at c.ij.oa.project.impl.ProjectUiFrameAllocator$run$progressRunner$1.apply(ProjectFrameAllocator.kt:96)
	at c.ij.oa.project.impl.ProjectUiFrameAllocator$run$progressRunner$1.apply(ProjectFrameAllocator.kt:72)
	at c.ij.oa.progress.impl.ProgressRunner.lambda$submit$3(ProgressRunner.java:244)
	at c.ij.oa.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:189)
	at c.ij.oa.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$12(CoreProgressManager.java:608)
	at c.ij.oa.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:683)
	at c.ij.oa.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:639)
	at c.ij.oa.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:607)
2

Hello @Datz,

I don’t see anything related to SonarLint in this strack trace, by any chance would you still have the complete one ?

3

Sorry, no. IntelliJ automatically created the ticket, so I think it must be related to the SonarLint plugin.

4

We had problems in the past where the JetBrains error reporting directed to the wrong plugin.

Without the full stack trace it’s hard to tell what the root cause is. If you ever notice the error again, could you please report back here with full details ?
Thanks!