Hey, thanks for the report. This is a known issue on Windows. The renderer process in Cursor hits the ~4 GB memory limit (an Electron limit on Windows) and crashes with an OOM error.
On version 2.4.27 there are two possible causes:
- Check for an OTEL memory leak:
- Open the Command Palette
Ctrl+Shift+P> Developer: Toggle Developer Tools > Console - Look for lines like
[otel.error]orOTLPExporterError - If you see them, it is a memory leak present in versions 2.3.35+
- Workarounds:
If you see OTEL errors:
- Downgrade to 2.3.34: Download · Cursor
- After installing: Settings > Application > Update > Mode: “none” (turn off auto-updates)
If you do NOT see OTEL errors:
- Rotate chats: start a new chat when the current one gets large (especially with agent workflows)
- Monitor memory:
Ctrl+Shift+P> Developer: Open Process Explorer, watch the renderer process - Check extensions: try
cursor --disable-extensionsfrom the command line
Related threads:
- Cursor IDE constantly crashing (same error code on 2.4.23)
- Constant OOM code 536870904 with latest update (fixed by starting a new chat)
- Windows Server 2022: Renderer OOM at ~3.8–4.0GB (code -536870904) → crash + state.vscdb.corrupted
I know this is frustrating, especially when working in plan mode. Let me know what you see in the console and whether the workarounds help.