Cursor crashes with "reason: 'oom'" when using Composer on Windows 11 RTX system

Hey, thanks for the report. The Renderer process in Cursor (Electron/Chromium) hits a hard hardware limit of about 4 GB of memory, then crashes with this OOM code. This does not depend on the total amount of RAM in your system.

I can see you have already tried a lot (reinstall, GPU acceleration, extensions, Early Access). Here is what else is worth checking:

  1. OTEL memory leak check:
    Ctrl+Shift+P > Developer: Toggle Developer Tools > Console. Look for lines with [otel.error] or OTLPExporterError. If you see them, that is an additional memory leak on top of the main limit.

  2. Workarounds that actually help:

  • Rotate chats. Start a new chat when the current one gets big, especially before long agent workflows.
  • Monitor memory: Ctrl+Shift+P > Developer: Open Process Explorer.
  • If it is already crashing on startup, delete recent chats via Chat History.

More discussion and context here: Cursor crashes repeatedly with out-of-memory (OOM) errors after the latest update, especially during large prompts or long-running plans

Let me know if you see any OTEL errors in the Console, and if rotating chats helps.