Hey there,
PHPStorm version: 2026.1
Plugin version: 2026.1.300
Terminal engine: Reworked 2025
My PHPStorm terminal seems super slow lately and sometimes completely locks up PHPStorm. I've also started seeing this warning:
Thread dump is here:
threadDump-20260423-112210-1776939730921.txt
The thread dump makes no sense to me, but asking GPT to parse it gave me this response:
My read: this does not look like a random JVM deadlock. It looks like PhpStorm’s UI is getting stuck waiting on a long-running indexing / PHP stub lookup path that is being triggered by the Symfony plugin’s command discovery, apparently from terminal command highlighting / Run Anything integration.
The key chain is:
The UI thread (AWT-EventQueue-0) is sitting inside JetBrains’ progress overlay machinery (SuvorovProgress / EventStealer), which usually means the IDE is waiting for some computation rather than hard-deadlocked.
A worker thread is deep in stub/index deserialization and file index updates: StubForwardIndexExternalizer, SerializedStubTree.restoreIndexedStubs, FileBasedIndexImpl.ensureUpToDate, PhpIndexImpl.getDirectSubclasses....
That index work flows straight into fr.adrienbrault.idea.symfony2plugin.util.SymfonyCommandUtil.getCommands, then SymfonyConsoleRunAnythingProvider.getValues, then RunAnythingTerminalBridge.matches, then TerminalShellCommandHandlerHelper.highlightCommandIfMatched. In plain English: typing or terminal command highlighting is causing the Symfony plugin to enumerate Symfony commands, which is forcing expensive PHP index work.
What I make of it:
Top suspect: Symfony plugin
The hottest meaningful stack in the dump points at fr.adrienbrault.idea.symfony2plugin. That plugin is not just present; it is on the active path that leads into expensive PHP index queries.
Secondary contributing factor: stale/corrupt/heavy indexes
The worker is doing a lot of stub forward-index restore/update work. Even if the plugin is the trigger, bad or huge indexes could be making the cost much worse.
The many TerminalEmulator-Local threads are probably noise
They are mostly blocked in native poll/read calls, which is normal for terminal I/O and not the smoking gun here.
My practical conclusion:
Most likely cause: Symfony plugin + PHP index lookup path triggered by terminal command matching/highlighting, with indexing overhead making the UI appear hung.
Let me know if there's any other info I can provide :)
Hey there,
PHPStorm version: 2026.1
Plugin version: 2026.1.300
Terminal engine: Reworked 2025
My PHPStorm terminal seems super slow lately and sometimes completely locks up PHPStorm. I've also started seeing this warning:
Thread dump is here:
threadDump-20260423-112210-1776939730921.txt
The thread dump makes no sense to me, but asking GPT to parse it gave me this response:
Let me know if there's any other info I can provide :)