VS Code Crash How to fix terminated unexpectedly oom error code 536870904

Hi Ross,

Having an associate blocked by constant crashes is incredibly frustrating. The "oom" (Out of Memory) reason combined with the error code -536870904 indicates that the underlying Electron framework (which powers VS Code) has exhausted its allocated memory limit.

Here is a step-by-step troubleshooting guide you can share with your team member to get them back up and running:

1. The Immediate Fix

Don't Restore Editors: When the error dialog in your screenshot appears, have them check the box that says "Don't restore editors" before clicking Reopen. Often, VS Code is trying to reload a massive file or a problematic workspace on startup, causing an infinite crash loop.

2. Identify the Root Cause

Massive Files: Ask if they are trying to open unusually large files (like gigantic .log files, massive .sql dumps, or heavily minified JavaScript). Opening these can instantly max out the V8 engine's memory stack.

Test Without Extensions: A rogue or poorly optimized extension (like a heavy linter or an AI autocomplete tool) might be leaking memory. Have them close VS Code, open a Command Prompt, and launch it in safe mode by typing: code --disable-extensions. If it remains stable, they will need to enable their extensions one by one to find the culprit.

Clear Workspace Cache: Corrupted index data can cause memory spikes. Have them close VS Code, navigate to C:\Users{Username}\AppData\Roaming\Code\User\workspaceStorage, and delete the folders inside.

3. Increase the Memory Limit (If Necessary)

If their project genuinely requires massive memory overhead (such as analyzing a massive monorepo), they can force VS Code to launch with a higher memory ceiling. From the terminal, they can launch it using:

code --max-memory=8192 (This allocates 8GB of memory).

Hope this helps