Cursor IDE constantly crashing

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When running agent, about every 15 minutes the Cursor IDE crashes with "The window terminated unexpectedly (reason: ‘oom’, code: ‘-536870904’).

Steps to Reproduce

I just have an agent running tasks, building code, and it regularly crashes, sometimes just after 3-5 minutes while running.

Expected Behavior

No crashing

Operating System

Windows 10/11

Version Information

Version: 2.4.23 (system setup)
VSCode Version: 1.105.1
Commit: 379934e04d2b3290cf7aefa14560f942e4212920
Date: 2026-01-29T21:24:23.350Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Opus 4.5

For AI issues: add Request ID with privacy disabled

Request ID: 7ccab9fe-2b7a-4192-895b-999900416f2b

Additional Information

this has just recently started a few days ago

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Cursor crashes repeatedly with out-of-memory (OOM) errors after the latest update, especially during large prompts or long-running plans
When the agent is running the analysis and coding the app crashes everytime
3

Hey, thanks for the detailed report. This is a known issue on Windows: the renderer process in Cursor hits the ~4 GB memory limit (an Electron limitation on Windows).

Based on version 2.4.23, there may be two factors:

1. Check for an OpenTelemetry memory leak:

  • Open the Command Palette Ctrl+Shift+P > Developer: Toggle Developer Tools > Console
  • Look for lines like [otel.error] or OTLPExporterError
  • If you see them, it’s a memory leak in versions 2.3.35+ that has been logged

2. Workarounds:

If you see OTEL errors:

  • Downgrade to 2.3.34: Download · Cursor
  • After installing: Settings > Application > Update > Mode: “none” (disable auto updates)

If there are no OTEL errors:

  • Rotate chats: start a new chat when the current one gets large (especially with agent workflows)
  • Monitor memory: Ctrl+Shift+P > Developer: Open Process Explorer, track the renderer process
  • Check extensions: try cursor --disable-extensions from the command line

Related threads with a similar issue:

Let me know what you find in the logs and whether the workarounds help.

4

This is a known Windows issue where the renderer process hits a ~4GB memory limit (Electron limitation). There’s a similar thread with workarounds:

  1. Check for OTEL errors: Ctrl+Shift+P > Developer: Toggle Developer Tools > Console - look for [otel.error] lines
  2. Rotate chats: Start a new chat when the current one gets large (this was the accepted solution for another user)
  3. Monitor memory: Ctrl+Shift+P > Developer: Open Process Explorer to watch the renderer process
  4. Test extensions: Run cursor --disable-extensions from command line to see if an extension is contributing

If you see OTEL errors, consider downgrading temporarily to 2.3.34 from Download · Cursor and disabling auto-updates.

5

Thanks for the quick and detailed info!

6

seeing lots of [otel.error] records. I will take the downgrade path for now. :slightly_smiling_face:

7

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.