-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Troubleshooting 1.41.1 crash on armv6l #1293
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
Comments
It's not the extensionHostWorker.js... I just re-tested in Firefox and that file loaded after just over 10 seconds on this test run. I'm wondering if node is aborting because of this assertion from the remoteagent.log |
Super helpful. Thanks for the report! cc: @sr229 |
This is a wontfix. We only support v12, and armv6l is EOL according to nodejs/nodejs.org#2205 |
Thanks for your help... the link you provided me lead me to the NodeJS Unofficial Builds site with builds of 12.14.1 for armv6. Upgrading to 12.14.1 resolved the issue and allowed code-server to work armv6! It runs just fine now. 😄 I'm on to the last issue which is memory usage being way too high for ram constrained systems... specifically how the build script buffers the entire binary in memory before writing it to disk... If I can replace that with a piped stream implementation(see solution #2), I think I should be able to build the standalone code server and package it on my 512MB Pi Zero 0 w. |
Glad to know. If you manage to come up with a binary let me know how it turns out. |
If possible, share us your steps so it can help us build code-server for armv7 @deftdawg, it'll be nice if we can build it for them since its been a blocker for us to build for 32-bit. |
[Related to efforts to get CS running on Arm 32-bit #35]
code-server
version: 1.41.1 commit f51e045Description
Code Server will crash after serving most of the VS Code UI.
Code Server starts normally.
Upon taking a request it, it returns the application to the requesting user agent.
Code Server will continue to respond to requests provided those requests aren't allowed to run to completion (navigate away and back before UI has totally loaded, or close tab and open another tap).
If the UI is allowed to load to completion a few seconds after the UI appears to have fully loaded, Code Server exits with status code 0. At this point the browser receives a dialog
Cannot reconnect. Please reload the window. [Reload Window] [Cancel]
More info
Browser developer tools show everything loading normally until this file:
http://localhost:8080/static-f51e045cd5483561afc07694f39307fb673b6d1d/out/vs/workbench/services/extensions/worker/extensionHostWorker.js
indicates it was cancelled with 0B having been received with a status of (cancelled) after 9.91 seconds.Remote Agent log (all of them look like this)
Here is the console data with all NODE_DEBUG turned on:
node-console-debug.log
Steps to Reproduce
If it would be helpful I make the build I'm working off available on my web server.
The text was updated successfully, but these errors were encountered: