Cursor keep on crashing

Support Bug Reports
,
6

Hey, this is a known issue on Windows. The renderer process hits the ~4 GB memory limit and crashes with that OOM error code.

A few things to try:

  1. Check for an OTEL memory leak: Open the Command Palette Ctrl+Shift+P > Developer: Toggle Developer Tools > Console tab. Look for [otel.error] or OTLPExporterError messages. If you see them, that’s a known memory leak.

  2. Rotate chats: If you’re running long agent sessions, start a new chat before they get too large. Long chat history is one of the main causes.

  3. Monitor memory: Ctrl+Shift+P > Developer: Open Process Explorer. Watch the renderer process. If it climbs toward 3.5 to 4 GB, start a fresh chat.

  4. Check extensions: Run cursor --disable-extensions from the command line and see if the crashes still happen.

  5. Clear workspace storage (nuclear option): Close Cursor, then delete the most recently modified folder in C:\Users\<your-username>\AppData\Roaming\Cursor\User\workspaceStorage. This resets your chat history and layout.

Also, how much RAM does your machine have? And does this happen more often during longer agent sessions?

The team is aware of this issue.

Related threads: