microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception Unhandled exception in [ComponentManager(ProjectImpl@703275169), com.intellij.codeWithMe.ClientIdContextElementPrecursor@7b229924, CoroutineName(com.intellij.codeInsight.navigation.CtrlMouseHandler2), Dispatchers.EDT] com.inte
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 262
- Forks
- 185
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
IntelliJ build version: 2024.3 IU-243.21565.193
OS: Mac OS X
JDK: JetBrains s.r.o. 21.0.5
Plugin version: 3.93.0-2024.3
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,0,0,2480x1395,layout=com.intellij.openapi.wm.impl.IdeRootPane$CustomHeaderRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]
Error message:
IdeaLoggingEvent[message=Unhandled exception in [ComponentManager(ProjectImpl@703275169), com.intellij.codeWithMe.ClientIdContextElementPrecursor@7b229924, CoroutineName(com.intellij.codeInsight.navigation.CtrlMouseHandler2), Dispatchers.EDT], throwable=com.intellij.openapi.util.TraceableDisposable$DisposalException: Editor is already disposed
at com.intellij.openapi.util.TraceableDisposable.throwDisposalError(TraceableDisposable.java:48)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported IntelliJ build, plugin version, operating system, and the stack trace showing TraceableDisposable disposal failure in CtrlMouseHandler2. Determine the interaction that accesses an already-disposed editor and reproduce it in the reported environment. Done means the unhandled exception no longer occurs during that interaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100