search

microsoft / vscode-remote-release

Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
https://aka.ms/vscode-remote
Other
3.68k stars 296 forks source link

[Remote-SSH Bug]: vscode server processes didn't closed after client closed. #10448

Closed pointertobios closed 2 weeks ago

pointertobios commented 2 weeks ago

Is there an existing issue for this bug?

Required Troubleshooting Steps

Connect Locally

It connects successfully

->

No response

Expected Behavior

server processes exit after client close

Steps To Reproduce

  1. Environment:
    • Server: Debian12
    • Client:Windows11
  2. Start a ssh remote vscode window.
  3. Close it.
  4. Link the server using ssh in the terminal.
  5. Check process.You will find many vscode related processes. Image

Remote-SSH Log

Remote-SSH Log

``` ```

Anything else?

No response

joshspicer commented 2 weeks ago

These processes will terminate after some time of no connection. Keeping the connection around for a limited amount of time provides a better experience if, say, you have an unstable internet connection.

If you need to kill the process sooner, i'd suggest using the built-in VS Code command to do so: Image

vs-code-engineering[bot] commented 2 weeks ago

The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.

Happy Coding!