java.lang.UnsupportedOperationException: Not implemented in c.ij.oa.ui.impl.GlassPaneDialogWrapperPeer
at c.ij.oa.ui.impl.GlassPaneDialogWrapperPeer.getOwner(GlassPaneDialogWrapperPeer.java:165)
at c.ij.oa.ui.DialogWrapper.getOwner(DialogWrapper.java:1212)
at c.ij.oa.progress.util.ProgressWindow.isPartOf(ProgressWindow.java:389)
at c.ij.oa.application.impl.LaterInvocator.isInModalContext(LaterInvocator.java:313)
at c.ij.oa.wm.impl.WindowCloseListener.windowClosing(ProjectFrameHelper.kt:453)
at java.desktop/java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:357)
at java.desktop/java.awt.Window.processWindowEvent(Window.java:2113)
at java.desktop/javax.swing.JFrame.processWindowEvent(JFrame.java:298)
at java.desktop/java.awt.Window.processEvent(Window.java:2072)
at java. Desktop/java.awt.Component.dispatchEventImpl(Component.java:5027)
at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2324)
at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2808)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4855)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:794)
at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:739)
at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:733)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
Do you remember if any specific actions triggered this UI freeze, or if a process within the IDE was running in the background for instance?
We would appreciate it if you could share the full stack trace, as well as the thread dumps when the UI freeze happens. You can follow this documentation to retrieve the dumps.
java.lang.Throwable: Slow operations are prohibited on EDT. See SlowOperations.assertSlowOperationsAreAllowed javadoc.
at c.ij.oa.diagnostic.Logger.error(Logger.java:376)
at c.ij.util.SlowOperations.assertSlowOperationsAreAllowed(SlowOperations.java:95)
at c.ij.workspaceModel.core.fileIndex.impl.WorkspaceFileIndexDataImpl.ensureIsUpToDate(WorkspaceFileIndexDataImpl.kt:128)
at c.ij.workspaceModel.core.fileIndex.impl.WorkspaceFileIndexDataImpl.getFileInfo(WorkspaceFileIndexDataImpl.kt:74)
at c.ij.workspaceModel.core.fileIndex.impl.WorkspaceFileIndexImpl.getFileInfo(WorkspaceFileIndexImpl.kt:239)
at c.ij.oa.roots.impl.ProjectFileIndexImpl.isUnderIgnored(ProjectFileIndexImpl.java:73)
at c.ij.oa.roots.impl.ProjectFileIndexFacade.isUnderIgnored(ProjectFileIndexFacade.java:71)
at c.ij.psi.impl.file.impl.FileManagerImpl.isExcludedOrIgnored(FileManagerImpl.java:418)
at c.ij.psi.impl.file.impl.FileManagerImpl.findDirectoryImpl(FileManagerImpl.java:404)
at c.ij.psi.impl.file.impl.FileManagerImpl.findDirectory(FileManagerImpl.java:397)
at c.ij.psi.impl.PsiManagerImpl.findDirectory(PsiManagerImpl.java:173)
at c.ij.psi.AbstractFileViewProvider.shouldCreatePsi(AbstractFileViewProvider.java:89)
at c.ij.psi.SingleRootFileViewProvider.createFile(SingleRootFileViewProvider.java:144)
at c.ij.psi.SingleRootFileViewProvider.getPsiInner(SingleRootFileViewProvider.java:101)
at c.ij.psi.AbstractFileViewProvider.getPsi(AbstractFileViewProvider.java:185)
Alright, I can test out any pre-release version if you have any avalible in the future.
Here’s another stack trace I got just now.
c.ij.oa.diagnostic.RuntimeExceptionWithAttachments: Read access is allowed from inside read-action or Event Dispatch Thread (EDT) only (see Application.runReadAction()); see https://jb.gg/ij-platform-threading for details
Current thread: Thread[AWT-EventQueue-0,6,main] 1480744024 (EventQueue.isDispatchThread()=true)
SystemEventQueueThread: (same)
at c.ij.util.concurrency.ThreadingAssertions.createThreadAccessException(ThreadingAssertions.java:149)
at c.ij.util.concurrency.ThreadingAssertions.softAssertReadAccess(ThreadingAssertions.java:107)
at c.ij.oa.application.impl.ApplicationImpl.assertReadAccessAllowed(ApplicationImpl.java:1013)
at c.ij.psi.impl.file.impl.FileManagerImpl.evaluateValidity(FileManagerImpl.java:588)
at c.ij.psi.impl.file.impl.FileManagerImpl.evaluateValidity(FileManagerImpl.java:584)
at c.ij.psi.impl.source.PsiFileImpl.isValid(PsiFileImpl.java:161)
at o.sl.ij.finding.LiveFinding.isValid(LiveFinding.java:130)
at o.sl.ij.ui.nodes.IssueNode.setIcon(IssueNode.java:127)
at o.sl.ij.ui.nodes.IssueNode.render(IssueNode.java:73)
at o.sl.ij.ui.tree.TreeCellRenderer.customizeCellRenderer(TreeCellRenderer.java:37)
at c.ij.ui.ColoredTreeCellRenderer.rendererComponentInner(ColoredTreeCellRenderer.java:125)
at c.ij.ui.ColoredTreeCellRenderer.getTreeCellRendererComponent(ColoredTreeCellRenderer.java:57)
at c.ij.ui.tree.ui.DefaultTreeUI.getRenderer(DefaultTreeUI.java:192)
at c.ij.ui.tree.ui.DefaultTreeUI.paint(DefaultTreeUI.java:338)
The 2023.3 version of IntelliJ, currently in EAP, received changes regarding the threading model. This requires modification on our side that we partly identified and that we are working on. While waiting for the next version of SonarLint, which should mitigate some of the issues you are facing, I invite you to switch to the latest non-EAP-released version of Rider, currently 2023.2.2. Also, please note that a lot of the issues present in the logs are not related to SonarLint.
Regarding java.lang.UnsupportedOperationException: Not implemented in c.ij.oa.ui.impl.GlassPaneDialogWrapperPeer, I couldn’t see a link with SonarLint with the given information we have. If any of you face this error again, please don’t hesitate to provide more details and the full stack trace.
Will you manage to release a fixed version by the time Rider 2023.3 goes public? If not, I’ll need to tell our coworkers to not update Rider for the time being.
Hi @MarkusSchaber, we have released SonarLint version 10.0, which should fix most of the issues regarding the latest EAP versions. Please come back to us if you find any other remaining problems that went under our radar.
Also, note that the EAP versions are constantly being updated every week, and due to the nature of our monthly release cadence, we cannot always fix the problems in time when they appear.
Hi, @nicolas.quinquenel,
I still get some freezes. However, I cannot yet definitely confirm that those are caused by SonarLint, as I don’t get the stack traces pointing to SonarLint as I did before the update.
Thank you for your feedback @MarkusSchaber, I am trying to identify any potential issue on our side.
If it ever happens again, please share with us a heap dump. It would be helpful for us to see any threading or memory issues. Also, in case of thread locks, IntelliJ automatically saves thread dumps into the logs directory, so do not hesitate to share this as well.
We have occasional freezes using SonarLint 10.0 on 2 machines here, using the Rider Versions 2023.2.3 and 2023.3 EAP 5 (233.11361.12).
We also had freezes using the previous SonarLint and Rider 2023.3 EAP 5 on my machine (the coworker didn’t try).
As far as we remember, the freezes did not happen with previous SonarLint version and Rider 2023.2.2 or older.
The updates to SonarLint 10.0 and Rider 2023.2.2 to 2023.2.3 happened at the same time, so we cannot pinpoint which of the two changes caused it.