Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Code-server instances "stay open" after being closed from browser

See original GitHub issue

OS/Web Information

Web Browser: Chrome
Local OS: Windows
Remote OS: Docker Linux
Remote Architecture: Docker Compose Contianer
code-server --version:

Steps to Reproduce

Open htop
Open multiple tabs and close them again when code-server loads
The instance stays open, with HTOP showing that the CPU usuage and RAM increases with each closed instance until it crashes.

Expected

The RAM and CPU usage should decrease after the instance is closed

Actual

It doesn’t 😃

Logs

https://files.mcaq.me/8xad.png I also don’t understand why the code-server items are tied to my user “adam” instead of root. This doesn’t make much sense to me?

This is difficult to show with logs, or at least I don’t know how to do it well with my setup.

Issue Analytics

State:
Created 2 years ago
Comments:10 (5 by maintainers)

Top GitHub Comments

2reactions

Sharpz7commented, Oct 29, 2021

Alright. So since upgrading to 3.12.0 I have not had this issue. There are two reasons why that could be the case:

Tabnine wasn’t the issue
3.11.1 was the issue (I think this is likely, I had tabnine in versions before this with no issues

Regardless, I do not have the time to test this completely, especially after I have just got 3.12.0 working.

Thanks for all the help

2reactions

geisericommented, Oct 15, 2021

This is 50% by design but also related to #3947. The idea is that you can keep a session alive, but you should be able to close the instance when you close the folder.