-
Notifications
You must be signed in to change notification settings - Fork 304
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
[Remote-SSH Bug]: Trying to connect to x86-64 Lima VM on ARM macOS host via Remote-SSH throws std::bad_alloc
when attempting to start VS Code server
#8391
Comments
Is it possible that your VM is out of memory? Any idea @deepak1556? |
Hi, thanks for getting back. I've had a look at my VM's memory using |
I have the same issue as far as I can guess on Colima and also on lima directly. In my case I am trying to run a dotnet docker container on a x86_64 lima VM. The same setup worked on the vz branch in December 2022 on an M1 Pro. So did anything change between now and then and does the CPU (now M2 Max) make a difference? Does anyone have any idea? |
I noted a similar error when running |
Are you able to run Node.js https://nodejs.org/download/release/v16.17.1/ on this VM ? |
In fact, I can't
Environment created in a Lima 0.15.1 (Both installed using Homebrew)
NodeJS downloaded with:
Also, it seems there is already a ticket on NodeJS for this issue: |
Thanks for confirming! We would have to wait for the upstream issue to be resolved. Can you try with docker instead, upstream issue seems to report it to be resolved there. |
Also found same problem reported here: nodejs/help#4156 My case is similar, |
I repeated this test on QEMU 8.0.3 and it seemed to work just fine. Maybe this was resolved on QEMU's side? |
@KuttKatrea My QEMU version is 8.1.1 and I'm still this experience this issue. Not sure about your Mac OS version tho, according to this thread lima-vm/lima#1605, This error might happens after MacOS 13.4 (mine is Mac 14.0) |
Since this was tracking an upstream issue, please let us know if this issue still persists. |
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue. Happy Coding! |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServer
settingConnect Locally
It connects successfully
->
No response
Expected Behavior
The Remote-SSH extension should be able to connect to the running Lima VM instance, and install and run the VS Code server successfully.
Steps To Reproduce
Failed to set up socket for dynamic port forward to remote port <port>: Socket closed. Is the remote port correct?
.~/.vscode-server/.<hash>.log
, the log mentions the server terminatingafter throwing an instance of 'std::bad_alloc'
.~/.vscode-server/bin/<hash>/out/server-main.js
will result in the same exception being thrown.Remote-SSH Log
Remote-SSH Log
Anything else?
~/.vscode-server/.<hash>.log
contents from VM after attempting to connect:I'm not sure of the exact cause of this, whether it could be the architecture, or something else, as there doesn't seem to be much information online regarding this issue with the Remote-SSH extension.
The text was updated successfully, but these errors were encountered: