Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple code-server instances #329

Closed
cTatu opened this issue Mar 24, 2019 · 5 comments · Fixed by #857
Closed

Multiple code-server instances #329

cTatu opened this issue Mar 24, 2019 · 5 comments · Fixed by #857

Comments

@cTatu
Copy link

cTatu commented Mar 24, 2019

Description

I deployed a code-server container to azure web services and had it running for 3-4 days. Along this days I was installing severals extensions (Python, GitLens, C/C++) and noticed now that there are multiple processes or instances of the code-server and don't know if it's normal.

List of processes in the azure container:
image

New fresh container in my local pc for compare:
image

Related Issues

Could this be causing this bug #328 ?

@cTatu cTatu added the question label Mar 24, 2019
@kylecarbs
Copy link
Member

kylecarbs commented Mar 24, 2019

These are all forked processes. Soon, the process-list will look more normal.

Edit: Actually, it's possible the extension host isn't being killed properly when a client exists. Will investigate.

@cTatu
Copy link
Author

cTatu commented Mar 24, 2019

Okey, I forgot to put the version I'm using: 1.32.0-310 from the latest release

@sr229
Copy link
Contributor

sr229 commented Mar 26, 2019

@kylecarbs sounds like a memory leak and a zombie process in one to me.

@RichardMcSorley
Copy link
Contributor

Consider using dumb-init or a process manager https://github.com/Yelp/dumb-init

@jaitaiwan
Copy link

I'm running the latest release and found that closing the client didn't end the processes (ubuntu 18.04) running via a systemd service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants