Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Orphaned process after closing the code-server browser tab

Open
#7,447 10 comments 1 reaction 1 assignee View on GitHub

@code-asher is already working on this.

Since Aug 14, 2025.

Assessment

This issue has not been assessed yet.

Description

bug triage
Is there an existing issue for this?
  • I have searched the existing issues
OS/Web Information
  • Web Browser: edge
  • Local OS: windows
  • Remote OS: linux
  • Remote Architecture: amd64
  • code-server --version: 4.100.0
Steps to Reproduce
  1. A standard scala project with metals and bloop
  2. kick off a run through vscode launch configs
  3. close the browser tab
Expected

All the processes launched by that browser sessions should be killed and cleaned up after the browser closure

Actual

The process are still running in the background with unclear states, and there is no way to "reconnect" to the orphaned processes

Logs

Screenshot/Video

No response

Does this bug reproduce in native VS Code?

No, this works as expected in native VS Code

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?
  • I am using a secure context.
Notes

I believe for vscode desktop, closing the editor will close all the "tasks" launched by vscode, but that doesn't appear to be the case for code-server. This applies to all the 3rd party extensions, and it is pretty bad because it basically leaks resources.

Also for certain applications that want to make sure there is only one process running at all time, and failure to clean up the resources actually impacts the functionalities.

Dominant language
TypeScript
Stars
79.4k
Forks
6.9k
Avg merge
2d 13h
Merged PRs (30d)
39

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/code-server

All issues in coder/code-server

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.