You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"Stopping extension hosts" takes a long time #6015
I've been seeing this message today whenever I close VS Code or change workspace.
At first I thought it was a VS Code issue, however microsoft/vscode#306129 mentions it might be related to extension child processes, and @zeikman noted in microsoft/vscode#305999 that it was being caused by this extension.
We do have a lot of processes that we try to clean up in deactivate(), but we should check whether this is all working correctly and whether any of them are slow to shut down.
@mariomakdis by "this extension" do you mean the Dart one?
My current theory is that many extensions are slow at shutting down, and VS Code used to hide/ignore this, but now they are waiting longer and showing this dialog.
I'm surprised they're not naming the extensions on that popup to help track down who's causing it though. You could try using VS Code's extension bisect to narrow down which extension is causing it for you.
It turns out that VS Code always allowed the full time to shutdown, but the recent change (which was a bug) was making the UI wait for it. So the next version of VS Code would've prevented this showing up, although in the background we still would've been hanging until it terminated us (but now we will not).
Activity
DanTup commentedon Mar 30, 2026
Seems like the Flutter daemon might not be terminating quickly, which might be causing this hold-up.
00xmario commentedon Mar 30, 2026
I don't have this extension installed and it still happens:

DanTup commentedon Mar 30, 2026
@mariomakdis by "this extension" do you mean the Dart one?
My current theory is that many extensions are slow at shutting down, and VS Code used to hide/ignore this, but now they are waiting longer and showing this dialog.
I'm surprised they're not naming the extensions on that popup to help track down who's causing it though. You could try using VS Code's extension bisect to narrow down which extension is causing it for you.
Fix hang during shutdown in Flutter workspaces
DanTup commentedon Mar 30, 2026
It turns out that VS Code always allowed the full time to shutdown, but the recent change (which was a bug) was making the UI wait for it. So the next version of VS Code would've prevented this showing up, although in the background we still would've been hanging until it terminated us (but now we will not).