Pylance still crashes after switching to my own Node.js executable #6983
Unanswered
nickchen120235
asked this question in
Q&A
Replies: 1 comment
-
For context my server is idling at around 3.8G of total used RAM when connected to and Pylance crashes at around 5.8G of total used RAM. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi community!
I recently experienced constant crashes in Pylance so I switched to my own Node.js, installed via nvm, following this troubleshooting guide. However, it still crashes because of allocation failed. I wonder if I misconfigured anything.
I use remote ssh to connect to the server. The server (actually a vm) has 16G of RAM and 16 CPU cores.
code --version
Pylance output
("service" has been renamed to protect private project)
Any help would be appreciated! Thanks!
Beta Was this translation helpful? Give feedback.
All reactions