Cursor crashes with “window terminated unexpectedly (reason: 'oom')”

[Raunak_Parmar]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Here’s an updated forum topic including your Cursor version details, ready to post:

---

Title: Cursor crashes with OOM error on Windows (v2.3.34)

Body:
Hi Cursor team and community,

I’m encountering frequent crashes in Cursor with the following error:

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

This causes Cursor to close abruptly while I’m working.

Environment details:

• Cursor version: 2.3.34 (user setup)
• VSCode version: 1.105.1
• Electron: 37.7.0
• Chromium: 138.0.7204.251
• Node.js: 22.20.0
• V8: 13.8.258.32-electron.0
• OS: Windows_NT x64 10.0.26200
• Date: 2026-01-10

Additional notes:

• The issue appears to be memory-related (oom = out of memory).
• Happens during normal usage (possibly when indexing or using AI features).
• Reopening sometimes restores editors, but the crash keeps recurring.

Has anyone faced a similar issue on Windows?
Are there recommended memory limits, flags, or known fixes?

Thanks for your help!

Steps to Reproduce

Here’s a clean “Steps to Reproduce” section you can add to your forum post or bug report:

---

Steps to Reproduce

1. Launch Cursor on Windows.

2. Open a large project/repository (for example, a Next.js or React project).

3. Start working normally (editing files, switching tabs, or using AI features).

4. Allow the project to finish indexing or trigger AI-assisted actions.

5. After some time, Cursor crashes and shows the error:

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

6. Reopen Cursor the issue may occur again after continued usage.

---

Expected Behavior

Cursor should remain stable and not crash during normal usage.

Actual Behavior

Cursor terminates unexpectedly with an out-of-memory (OOM) error.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Cursor version: 2.3.34 (user setup)

VSCode version: 1.105.1

Electron: 37.7.0

Chromium: 138.0.7204.251

Node.js: 22.20.0

V8: 13.8.258.32-electron.0

OS: Windows_NT x64 10.0.26200

Date: 2026-01-10

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. This is a known issue in 2.3.x, and the team is working on a fix for a few memory leaks.

A few questions to help us debug:

1. What’s the size of your project, roughly how many files?
2. Can you open CTRL + Shift + P, then Developer: Open Extension Monitor. Do any extensions show high memory usage?
3. Please open CTRL + Shift + P, then Developer: Open Process Explorer. Go to the Memory History tab and click Save in the top bar. This will help the team see which process is using the memory.

Temporary workaround: Make smaller changes and commit more often to reduce the chance of a crash.

Send the details for 1-3 and it’ll help the team look into your specific case.

[Raunak_Parmar]

Total number of lines are this 2,14,595, excluding the folders like .next, node_modules, .git and virtualenv

I’m using Fast API and nextjs to build my application and now this application has became too big with lot of features.

I tried to open Developer: Open Extension Monitor but i didn’t see this option. so i have attached the below explorer.

my history tab is always shown as below.