Critical OOM Crash Issue on Windows – Cursor IDE Keeps Closing

Support Bug Reports
, , ,
3

Hey, thanks for the report. This is a known issue on Windows. The renderer process in Cursor (Electron) is limited to about 4 GB of memory. This is an architectural limit and doesn’t depend on how much RAM your machine has.

Here are a few things you can try:

  1. Check for an OTEL memory leak: press Ctrl+Shift+P > Developer: Toggle Developer Tools > Console. Look for lines like [otel.error] or OTLPExporterError. If you see them, it’s likely a memory leak present in versions 2.3.35+.

  2. Rotate chats. Don’t let a single chat get too large. Start a new chat before big tasks. You can watch memory usage via Ctrl+Shift+P > Developer: Open Process Explorer. If the renderer is getting close to 3.5 GB, it’s time to start a new chat.

  3. Check extensions. Run cursor --disable-extensions from the command line and see if the issue changes.

  4. Deleting old chats can also help via the Chat History panel.

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

The team is aware of the issue. There’s no timeline yet, but every report helps with prioritization.

Let me know if these workarounds helped.