Error Code : -536870904

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Pretty much anything i do in cursor, I get this error “The windows terminated unexpectedly (reason: ‘oom’,code:‘-536870904’) . We are sorry for the inconvenience. you can reopen the window to continue where you left off.”

Steps to Reproduce

As soon as i type a command on the project i am working on, i get cursor to shutdown and gives me this same error.

Expected Behavior

Cursor is supposed to work without crashing everytime.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.2.11 (user setup)
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Auto

Additional Information

Just need help with cursor not crashing almost evertime i work with it.

Does this stop you from using Cursor

Yes - Cursor is unusable

This is what i see in console:

What is see in Process Explorer

Hey, thanks for the report, a few things stood out:

  1. There are lots of third party extensions in the log: github.copilot-chat, ms-python, ms-toolsai.datawrangler, and a bunch of Azure and Java ones. github.copilot-chat is known for memory leaks in Electron apps and it can also conflict with Cursor Agent. Try launching Cursor with extensions disabled and see if the crash still happens in the same scenario:

    cursor --disable-extensions
    

    If the crash goes away, turn extensions back on one by one to find the one causing it.

  2. HOOKS Failed to parse project hooks configuration means the project has a broken hooks config. Check .cursor/hooks.json or hooks.yaml in the repo root and also in ~/.cursor/ and either delete or fix it.

  3. Process Explorer: in your screenshot the renderer window is steady at about 702 MB. To catch a leak, open Process Explorer ahead of time, switch to the History (Mem) tab, and use Cursor normally. Right before the crash you should see which process is growing, usually the one with the Agent chat open.

  4. In the crash dialog, tick “Don’t restore editors” before you click Reopen. Session restore often triggers the same crash again via the same extensions.

Let me know what History (Mem) shows right before the crash, and whether --disable-extensions helps.