Hey, this is a known issue on Windows. The renderer process can hit Electron’s memory limit of about 4 GB during long agent sessions and then crash with an OOM error.
A few things to try:
-
Check for an OTEL memory leak: Open
Ctrl+Shift+P> Developer: Toggle Developer Tools > Console. Look for lines like[otel.error]orOTLPExporterError. If you see them, that’s a known memory leak that can make crashes more likely. -
Rotate chats: Don’t let a single chat session get too large. Start a new chat from time to time, especially for heavy agent workflows with Opus or Sonnet.
-
Check extensions: Try running
cursor --disable-extensionsfrom the command line to rule out extension memory usage.
Related threads with the same issue:
- Cursor crashes repeatedly with out-of-memory (OOM) errors after the latest update, especially during large prompts or long-running plans
- Cursor IDE constantly crashing
The team is aware of the issue. Let me know what you see in the Developer Console and whether rotating chats helps.