Critical OOM Crash Issue on Windows – Cursor IDE Keeps Closing

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hello,

I am a Pro+ subscriber. I would like to report a persistent and critical issue with Cursor IDE on Windows.

Every few minutes, I receive the following error message:

“The window terminated unexpectedly (reason: ‘oom’, code: -536870904)”

After this alert appears, the Cursor IDE closes automatically. This happens repeatedly and makes it impossible to work properly.

I have been dealing with this issue for a long time. Unfortunately, recent updates have not resolved the problem. The crashes continue to occur frequently.

I am using:

Windows environment

Paid plan (active subscription)

This has become extremely disruptive to my workflow. I rely on Cursor for development, but the constant OOM crashes are making it very difficult to continue using it productively.

Please investigate this issue as a priority. If needed, I can provide:

Logs

System specifications

Reproduction steps

Any additional diagnostic information

Looking forward to your assistance.

Best regards,

Steps to Reproduce

  1. Open Cursor IDE on Windows.
  2. Open any project (this happens regardless of project size).
  3. Start normal development work (editing files, using AI features, navigating between files).
  4. After a few minutes (sometimes even without heavy usage), the IDE crashes.
  5. An alert appears saying: “The window terminated unexpectedly (reason: ‘oom’, code: -536870904)”.
  6. Cursor closes automatically.
  7. The issue repeats every few minutes after reopening.

The issue happens more frequently when using AI features (chat, code generation, or large file analysis).

Expected Behavior

Cursor IDE should remain stable and not crash during normal usage.

The application should not run out of memory under regular development conditions. Even when using AI features, it should handle memory safely without terminating unexpectedly.

Screenshots / Screen Recordings

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.png
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.png566×184 6.27 KB

Operating System

Windows 10/11

Version Information

Version: 2.4.37 (user setup)
VSCode Version: 1.105.1
Commit: 7b9c34466f5c119e93c3e654bb80fe9306b6cc70
Date: 2026-02-12T23:15:35.107Z
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

Does this stop you from using Cursor

No - Cursor works, but with this issue

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.