UI Stops responding

Update, the server DOES stop when asked, but since the rest of the UI is unresponsive, I have to kill it and restart the IJ UI

UI Support team here.
Please share your logs (go to main menu **"Help | Collect logs and diagnostic data "** and send us the zip). Upload the logs to https://uploads.jetbrains.com/  and share the upload ID here.

Currently, we have no known issues with a similar impact affecting common known environments, so we must have more information to continue the investigation.

here is a log
2026_05_09_27T4ANhoTqJzxyCcF13XUH 

I understand this is on a older IDE but I can't control the version

here is another one
2026_05_09_QWWYEcge6YY4qLxNkH6uvT 

it is very frustrating how often this happens

Hi Troy,

The idea.log file does not contain freeze information. From the log itself, I can say, that multiple plugin errors were reported by OS Gosu plugin, and some of the indices were broken.

Recommendations:

1. Disable all third-party plugins 
2. Re-index the IDE with the main menu “File | Invalidate caches”

If the steps above did not help, please send us the complete logs with main menu "Help | Collect logs and diagnostic data" and send us the entire zip (not only idea.log file)

i can't really disable the Gosu plugin because without it nothing works. This is Guidewire Studio and it editing their system. When I run Collect logs, all i get is the log. there is no zip file. My best guess is it gets so locked up that even that feature doesn't work. As I mentioned, I have to kill it from TM so it would make sense that even the diag tool would not work. I am at a loss. And it only recently started doing this (5 months)

I will see if i can find a pattern and get logs if possible. I will also try invalidate cache.

Here is the the first message in the line of log error messages:

2026-05-09 14:50:07,799 [17232058] SEVERE - #c.i.o.a.i.FlushQueue - Element: class gw.gosu.ij.psi.impl.source.GosuPsiExpressionCodeFragmentImpl #Gosu  because: invalid context: parent is null
-
invalidated at: no info; Cached PSI
com.intellij.psi.PsiInvalidElementAccessException: Element: class gw.gosu.ij.psi.impl.source.GosuPsiExpressionCodeFragmentImpl #Gosu  because: invalid context: parent is null
invalidated at: no info; Cached PSI
    at com.intellij.psi.impl.PsiDocumentManagerBase.ensureValidFile(PsiDocumentManagerBase.java:108)
    at com.intellij.psi.impl.PsiDocumentManagerBase.getPsiFile(PsiDocumentManagerBase.java:93)
    at com.intellij.psi.impl.PsiDocumentManagerImpl.getPsiFile(PsiDocumentManagerImpl.java:62)
    at org.jetbrains.java.debugger.JavaDebuggerEditorsProvider.createExpression(JavaDebuggerEditorsProvider.java:62)
    at com.intellij.xdebugger.impl.ui.XDebuggerExpressionComboBox$XDebuggerComboBoxEditor.getItem(XDebuggerExpressionComboBox.java:267)
    at com.intellij.xdebugger.impl.ui.XDebuggerExpressionComboBox.getExpression(XDebuggerExpressionComboBox.java:141)
    at com.intellij.xdebugger.impl.ui.XDebuggerEditorBase.setSourcePosition(XDebuggerEditorBase.java:192)
    at com.intellij.xdebugger.impl.frame.XWatchesViewImpl.buildTreeAndRestoreState(XWatchesViewImpl.java:307)
    at com.intellij.xdebugger.impl.frame.XVariablesView.lambda$processSessionEvent$0(XVariablesView.java:78)
    at com.intellij.util.concurrency.ContextRunnable.run(ContextRunnable.java:27)

From this log, I can say that Gosu plugin referred to non-existing document structure PSI item. Additional investigation is below.

Why the PSI file becomes invalid

The document was originally created in XDebuggerEditorsProviderBase.createDocument() → JavaDebuggerEditorsProvider.createExpressionCodeFragment(XExpression, ...) (line 73-81), which calls factory.createPresentationPsiCodeFragment(text, context, project). The Gosu plugin's CodeFragmentFactory creates a GosuPsiExpressionCodeFragmentImpl as the code fragment, and the document is derived from its ViewProvider.

The Gosu PSI code fragment becomes invalid later (the error message says "containing file is null" and "context=null, contextFile=null"). This can happen when the debugger context changes (e.g., stepping, frame switching), the PSI context element gets invalidated, or the Gosu plugin doesn't properly maintain the code fragment's validity. The PSI hierarchy shown in the error (GosuPsiIfStatementImpl → GosuPsiCodeBlockImpl → etc.) suggests the original context element in the Gosu source file was invalidated (possibly due to a reparse or file change), and this invalidation propagated to the code fragment.

However, we agree that the plugin error should not hang up the UI. I filed a new ticket IDEA-389329, please upvote to follow the updates.