Hey, thanks for the report. This is a known Windows issue where the renderer process in Cursor hits a ~4 GB memory limit (an Electron limitation on Windows).
Related threads with fixes:
- Windows Server 2022: Renderer OOM at ~3.8–4.0GB (code -536870904) → crash + state.vscdb.corrupted
- OOM problems persist in Cursor 2.3 despite available memory
Try this workaround.
Check the logs for OTEL errors:
- Open the Command Palette
Ctrl+Shift+P> Developer: Toggle Developer Tools > Console - Look for lines with
[otel.error]orOTLPExporterError - If you find them, it’s an OpenTelemetry memory leak in your version 2.4.21
If you DO see OTEL errors:
- Downgrade: there isn’t an official downgrade path yet, but you can download an older version directly from Download · Cursor (look for 2.3.34)
- After installing: Settings > Application > Update > Mode: “none” (disable auto-update)
If you DON’T see OTEL errors:
- Monitor memory:
Ctrl+Shift+P> Developer: Open Process Explorer, then watch the renderer process - Rotate chats: start a new chat when the current one gets big (avoid building up too much context)
- Check extensions: try running
cursor --disable-extensionsfrom the command line
Let me know what you find in the logs and whether this helps.