VS Code exited unexpectedly with code 0

[rschroll]

This appears to be the same problem as #3198, but with a different version of code-server. I'm opening a new bug to avoid confusing that one, but I'm happy to have them merged together if you feel it's the same underlying problem.

OS/Web Information

• Web Browser: Chrome 91.0.4472.81
• Local OS: ChromeOS 91.0.4472.81
• Remote OS: Raspbian 10
• Remote Architecture: armv7l
• code-server --version: 3.10.2 387b12e

Steps to Reproduce

1. Launch code server with code-server ---auth none --bind-addr 0.0.0.0:8080 -vvv.
2. Visit port 8080 on the server.

Expected

VS Code

Actual

500

Logs

Console output

[2021-06-13T22:37:30.197Z] trace child:18671 got message {"message":{"type":"handshake","args":{"_":[],"bind-addr":"0.0.0.0:8080","auth":"none","password":"d1a25a44f29fe7aabf39b4f2","config":"/home/pi/.config/code-server/config.yaml","verbose":true,"user-data-dir":"/home/pi/.local/share/code-server","extensions-dir":"/home/pi/.local/share/code-server/extensions","log":"trace","host":"0.0.0.0","port":8080,"proxy-domain":[],"usingEnvPassword":false,"usingEnvHashedPassword":false}}}
[2021-06-13T22:37:30.211Z] info  code-server 3.10.2 387b12ef4ca404ffd39d84834e1f0776e9e3c005
[2021-06-13T22:37:30.213Z] info  Using user-data-dir ~/.local/share/code-server
[2021-06-13T22:37:30.214Z] trace Using extensions-dir ~/.local/share/code-server/extensions
[2021-06-13T22:37:30.281Z] info  Using config file ~/.config/code-server/config.yaml
[2021-06-13T22:37:30.282Z] info  HTTP server listening on http://0.0.0.0:8080 
[2021-06-13T22:37:30.282Z] info    - Authentication is disabled 
[2021-06-13T22:37:30.283Z] info    - Not serving HTTPS 
[2021-06-13T22:38:38.836Z] trace heartbeat
[2021-06-13T22:38:38.888Z] debug forking vs code...
[2021-06-13T22:38:40.719Z] error VS Code exited unexpectedly with code 0

Refreshing the web browser results in

[2021-06-13T22:39:37.995Z] debug forking vs code...
[2021-06-13T22:39:38.842Z] debug 2 active connections
[2021-06-13T22:39:38.843Z] trace heartbeat
[2021-06-13T22:39:39.877Z] error VS Code exited unexpectedly with code 0

The most recent files from ~/.local/share/code-server/coder-logs.

Both the stderr and stdout files are empty.

The browser console.

raspberrypi.local/:1 GET http://raspberrypi.local:8080/ 500 (Internal Server Error)
logger.ts:173 error [Service Worker] navigator is undefined

The browser network tab.

I have the .har file, but Github won't let me upload it. It shows what you would expect, though: a 500 from the server followed by 200s for the various resources used by the 500 page.

Screenshot

It's a 500 page.

Notes

This issue can be reproduced in VS Code: No (I cannot run VS Code headless.)

I had previously been running code-server 3.7.4, but often running into problems with the Jupyter extension not loading properly (#2341). Upgrading code server (npm update -g code-server) resulted in a broken install, so I uninstalled and reinstalled (npm install -g code-server), resulting in this problem.

I've moved ~/.local/share/code-server from the previous installation to another location, and the problem persists.

[jsjoeio]

Thank you @rschroll for the thorough report (and linking to the other issue).

We'll have to grab a Pi and look more into this. About a month ago, I was able to get code-server working on my Pi (installing via npm) so I'm not sure what we changed that would break it.

We have other priorities at the moment but I will add this to "On Deck" and hopefully we can get to it after this current milestone. Thanks for your patience!

[F-Unction]

Same error on termux, requires help!

[rschroll]

I just tried installing code-server 3.11.0, and it seems to be working. Perhaps this issue should be closed?

[jsjoeio]

Great! We will close then. For the others, if you experience this again, please open a new bug report with repro steps!

[notthetup]

Hey folks, I encountered the EXACT same error except it was on version 3.11.1. Downgrading to 3.11.0 solved it though.

So somehow 3.11.1 has regressed?

[jsjoeio]

@notthetup can you please open a new bug report with repro steps?