extensionHost debugger stays alive after window was closed

[eliericha]

• VSCode Version: 1.92.2
• Local OS Version: macOS Sonoma 14.6.1 (23G93)
• Remote OS Version: Ubuntu 20.04.6 LTS
• Remote Extension/Connection Type: SSH

• Logs:

Logs from 'Server' Output Channel in VS Code

2024-08-27 14:40:34.808 [info] [<unknown>][70e70e6e][ManagementConnection] New connection established.
2024-08-27 14:40:34.816 [info] [<unknown>][b445fd92][ExtensionHostConnection] New connection established.
2024-08-27 14:40:34.821 [info] [<unknown>][b445fd92][ExtensionHostConnection] <2095036> Launched Extension Host Process.
2024-08-27 14:40:34.842 [info] [<unknown>][b445fd92][ExtensionHostConnection] <2095036><stderr> Debugger listening on ws://127.0.0.1:53853/f3ef3228-222d-4d81-aef6-3bd396e1939b
For help, see: https://nodejs.org/en/docs/inspector

2024-08-27 14:40:34.921 [info] [<unknown>][b445fd92][ExtensionHostConnection] <2095036><stderr> Debugger attached.

2024-08-27 14:40:35.018 [info] Loading development extension at /home/richa/ancr/src/vscode-extension-samples/quickinput-sample
2024-08-27 14:40:36.289 [info] Extension signature verification result for dbaeumer.vscode-eslint: Success. Executed: true. Duration: 240736ms.
2024-08-27 14:40:36.320 [info] Extracted extension to file:///home/richa/.vscode-server/extensions/dbaeumer.vscode-eslint-3.0.10: dbaeumer.vscode-eslint
2024-08-27 14:40:36.349 [info] Renamed to /home/richa/.vscode-server/extensions/dbaeumer.vscode-eslint-3.0.10
2024-08-27 14:40:36.358 [info] Extension installed successfully: dbaeumer.vscode-eslint file:///home/richa/.vscode-server/extensions/extensions.json
2024-08-27 14:40:53.780 [info] [<unknown>][70e70e6e][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
2024-08-27 14:41:12.376 [info] [<unknown>][b445fd92][ExtensionHostConnection] <2095036><stderr> Debugger ending on ws://127.0.0.1:53853/f3ef3228-222d-4d81-aef6-3bd396e1939b
For help, see: https://nodejs.org/en/docs/inspector

2024-08-27 14:41:12.436 [info] [<unknown>][b445fd92][ExtensionHostConnection] <2095036> Extension Host Process exited with code: null, signal: SIGTERM.

Steps to Reproduce:

1. Open a remote workspace of a VS Code extension, e.g. the quickinput-sample project from the extension samples repository
2. Hit F5 or use the Debug: Start Debugging command
3. The extensionHost debugger is started, a new VS Code window appears connected to the debugged extension host. All is well so far.
4. Close the debugged VS Code window.
5. The debugger stays alive even thought the debugged window was closed.
6. It is no longer possible to start new debug sessions, until the debugger is killed manually.

I have seen similar issues when starting a debug session using the Extension Test Runner over a remote connection. Here the problem is more serious. The debugged window gets disconnected at the end of the test and hangs. I can no longer close it. Starting tests tries to use the same window and hangs. The session is sort of useless at that stage and I have to kill the server and restart from scratch.

But that seems like a more complex problem so I think it's best to start with the first issue which doesn't involve the Extension Test Runner.

Does this issue occur when you try this locally?: No Does this issue occur when you try this locally and all extensions are disabled?: No

Thanks!

[eliericha]

The issue disappeared after updates of VS Code and/or the Remote extension so we can close this.