Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Orphaned process after closing the code-server browser tab

Abierto
#7,447 10 comentarios 1 reacción 1 asignado Ver en GitHub

@code-asher ya está trabajando en esto.

Desde el 14/8/2025.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
79.4k
Forks
6.9k
Merge medio
2 d 13 h
PR fusionados (30 d)
39

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de coder/code-server

Todos los issues de coder/code-server

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.