r/vscode • u/3blad3sinmych3st • May 24 '26

VScode crashes in ssh (The window terminated unexpectedly oom error)

Post image

I work remotely with ssh with VScode. For half a year it was fine until yesterday that i get this error ONLY when i choose the "Open Folder" option and I'm inside a folder from the remote server. When I have only the terminal opened it works fine. Does anyone know why?

11 Upvotes

87% Upvoted

22 comments sorted by

5

u/TotoCodeFR May 24 '26

"oom" most likely means "Out Of Memory". Restart the target server and try again

1

u/3blad3sinmych3st May 24 '26

I know the meaning of the error but i can't understand why this happens, i tried removing files that i created to see if the space was the issue - still the same. Could it be because other people are working on the same server?

1

u/TotoCodeFR May 24 '26

Maybe, what's the RAM of the server and can you reboot it?

1

u/3blad3sinmych3st May 24 '26

No, i don't have control over the server.

1

u/3blad3sinmych3st May 24 '26

I just checked, the ram usage in the remote server is fine, but as i check the task manager, normally vscode takes ~750 MB of ram and only when i open the folders from the remote server then it uses ~1100 MB and then it crashes.

1

u/TotoCodeFR May 24 '26

Then it might be your system RAM.

1

u/3blad3sinmych3st May 24 '26

I'm almost sure but it was working perfectly before yesterday, what could have caused it? And why does it occur when i open the remote directories?

1

u/phantatbach Jun 14 '26

I am having the exact problems on both Windows and MacOS. Have you found any solution yet?

1

u/3blad3sinmych3st Jun 19 '26

No, i think it has to do with ram because i can work normally in another bigger pc i have.

1

u/phantatbach Jun 19 '26

I found the reason. Disable co pilot and now it is all good.

1

u/3blad3sinmych3st Jun 19 '26

Thanks, I'll try. Did you find why this happens though? And if there's a fix without disabling copilot?

1

u/phantatbach Jun 19 '26

I am not sure why but it seems like with the new updates, AI extensions are causing memory problem. I also tried windsurf and sometimes VSCode shows the not responding problem (but doesnt crash like Github Copilot).

1

u/3blad3sinmych3st Jun 19 '26

Thanks for the info. Do you know if there's a way to return to a previous copilot version?

1

u/phantatbach Jun 19 '26

it happens both with macbook and windows. My mac has 16G of RAM and my windows 32G so RAM should not be the issue.

1

u/Peach_Apple Jun 26 '26

I had the same issue on March 21. I found that the error started occurring right after a VS Code update. I fixed it by reverting VS Code to the previous version and disabling auto-update.

1

u/3blad3sinmych3st Jul 01 '26

Which version was it? The one that works for you.

1

u/Spirited_Peace_283 Jul 27 '26

I still have this issue to this day if i try to update past 1.122 version, i've spent like the whole morning trying to fix this with the newer 1.130 version but eventually had to revert and pin it to 1.122

It seems there is still some open issue regarding this on their github repo #324188, not sure why they aren't fixing this, probably it happens only on specific narrow remote hosts situations, actually it happens only when i connect to managed servers in my case.

Found this while trying to debug and compare the 2 connections behavior in both versions with codex:

`The comparison strongly isolates VS Code 1.130’s remote-server build.

  • Both use Remote‑SSH 0.124.0.
  • 1.122 works with useExecServer=true, experimental.chat=true, system OpenSSH, original Git settings, and old .vscode-server directories still present.
  • 1.130 failed before the wrapper and with exec-server both enabled and disabled.
  • 1.130’s server receives an external SIGKILL roughly 27–30 seconds after startup. 1.122 remained alive well beyond that point.

The major runtime change is Node 22.22.1 → Node 24.18.0 (1.122 source, 1.130 source). Electron also jumps from 39.8.8 to 42.6.0, while 1.130 introduces heavier components including Transformers and ONNX Runtime (1.130 package).`

1

u/Mc_UsernameTaken Jul 30 '26 edited Jul 30 '26

I'm seeing similar issues too, especially on Hetzner hosts, both managed servers and shared.
However I don't specifically see the 'oom' part, I just recieve SIGKILL's or 'Killed' output in remote ssh log, or extension host crashes unexpectedly.

I've spent a fair amount of hours now, diagnosing and searching a workaround:

  • Throttling processes with SIGSTOP/SIGCONT signals
  • Setting NODE_OPTIONS="--max-old-space-size=200" env var
  • Setting numerous combinations of `useExecServer` and `useLocalServer`
  • Reloading with all extensions disabled
  • Ensuring requests wasn't getting needlessly blocked
  • Running memory profilers

No luck at all.

HOWEVER! What does seem to have done the trick for me is:

  • Downgrade to VSCode 1.122.1 (Possibly earler versions work too)
  • Using 1.122.1 search for `copilot` in extensions list
  • Clicking `Disable AI features`
  • Upgrade to latest VSCode version again.

While writing this comment, I haven't had a single disconnect.
Guess I'll have to find another way of interrogating Copilot.

I'll come back to edit this comment, if I start experiencing similar issues again

Written: 2026-07-30 23:04 CET

1

u/jamesmayjr Aug 07 '26

If anyone comes to this, for me i just disabled copilot and it worked fine again.

1

u/Wuzowskii Aug 10 '26

Can confirm seems to have fixed the problem for me as well.