# Renderer OOM crash (code -536870904) every ~3 minutes on Windows — 128GB RAM, reproducible

**URL:** <https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534>\
**Category:** Bug Reports\
**Tags:** performance, windows, crashes, chat\
**Created:** [February 21, 2026, 8:52pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534 "2026-02-21T20:52:27Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Silly\_Spicee](https://avatars.discourse-cdn.com/v4/letter/s/bc79bd/32.png) [@Silly\_Spicee](https://forum.cursor.com/u/Silly_Spicee)\
**Post date:** [February 21, 2026, 8:52pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/1 "2026-02-21T20:52:27Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

## Environment

- **Cursor version:** 2.5.20 (stable, commit 511523af)
- **OS:** Windows 11 Pro Build 26200
- **CPU:** AMD Ryzen Threadripper 3970X (32-core)
- **GPU:** NVIDIA GeForce RTX 5080
- **RAM:** 128 GB (76+ GB free at time of crash)
- **Page file:** 32 GB (increased from 8 GB, did not help)

## Problem

Cursor renderer process crashes with OOM every ~3 minutes consistently.  
Error: `The window terminated unexpectedly (reason: 'oom', code: '-536870904')`

The same workflow on Ubuntu (same machine, dual-boot) does NOT produce this error.

## Reproduction

1. Open Cursor on any project (even a small 36-file Android/Gradle project)
2. Open Agent chat and send a few messages
3. Wait ~3 minutes
4. Crash: `CodeWindow: renderer process gone (reason: oom, code: -536870904)`

Happens 100% of the time. Crash loop — reopening leads to another crash in ~3 min.

## Diagnostic data

### Renderer memory growth (observed live via Get-Process)

The renderer process responsible for the Agent chat window grows rapidly:

- T+0 min: ~600 MB
- T+2 min: ~3000 MB (3 GB)
- T+4 min: ~5100 MB (5.1 GB)
- T+5 min: CRASH (OOM)

Other renderer processes stay stable at 200-600 MB.

### main.log (consistent pattern across sessions)

2026-02-21 18:59:40.988 [error] CodeWindow: renderer process gone (reason: oom, code: -536870904)  
2026-02-21 19:06:02.421 [error] CodeWindow: renderer process gone (reason: oom, code: -536870904)

### Renderer command line (js-flags NOT passed to renderer)

`--max-old-space-size=65536` set in argv.json does NOT appear in renderer process  
command line. The flag only affects the main process, not the renderer.

### Process snapshot at time of investigation

ProcessId WorkingSet\_MB Type  
71536 5146 renderer ← this one crashes  
62916 625 renderer  
60664 445 gpu-process  
71176 260 main

## What I already tried (none helped)

1. ✗ `argv.json`: `"js-flags": "--max-old-space-size=65536"` — does not affect renderer
2. ✗ `argv.json`: `"disable-hardware-acceleration": true` — crash still happens
3. ✗ `--disable-extensions` — crash still happens (Agent is built-in)
4. ✗ Cleared CachedData, GPUCache, Cache directories
5. ✗ `settings.json`: `"window.restoreWindows": "none"`
6. ✗ Created `.cursorignore` excluding build dirs (project only has 36 files)
7. ✗ Increased page file from 8 GB to 32 GB
8. ✗ Extended `files.watcherExclude`

## Key observations

- Crash is **Windows-specific** — same machine on Ubuntu works fine
- Crash happens in **renderer process** , not main or extension host
- `js-flags` from `argv.json` do NOT propagate to renderer processes
- Indexing completes in 3 seconds (36 files) — not the cause
- 128 GB RAM with 76+ GB free — not a system memory issue
- The leaking renderer is always the one running Agent chat
- Multiple windows (3-4) accelerate the issue but single window also crashes

## Expected behavior

Renderer process should not grow unbounded. Either implement memory limits for  
renderer processes or fix the memory leak in the Agent chat rendering pipeline.

### Steps to Reproduce

1. Fresh install Cursor 2.5.20 on Windows 11 (128 GB RAM, RTX 5080)
2. Open any project (even small — 36 files Android/Gradle project)
3. Open Agent chat (Ctrl+L or Cmd+L)
4. Send 3-5 messages in Agent mode
5. Wait ~3 minutes
6. Renderer process grows from 600 MB → 3 GB → 5 GB → crash
7. Dialog appears: “The window terminated unexpectedly (reason: ‘oom’, code: ‘-536870904’)”
8. Click “Reopen” — crash repeats in ~3 minutes again (crash loop)

Note: Does NOT reproduce on Ubuntu (same hardware, dual-boot). Windows-only.

### Operating System

Windows 10/11

### Version Information

Version: 2.5.20 (user setup)  
VSCode Version: 1.105.1  
Commit: 511523af765daeb1fa69500ab0df5b6524424610  
Date: 2026-02-19T20:41:31.942Z  
Build Type: Stable  
Release Track: Default  
Electron: 39.4.0  
Chromium: 142.0.7444.265  
Node.js: 22.22.0  
V8: 14.2.231.22-electron.0  
OS: Windows\_NT x64 10.0.26200

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [February 23, 2026, 7:26pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/4 "2026-02-23T19:26:32Z")

</div>

Hey there! Thanks for reporting. I private messaged you some instructions for grabbing a performance trace. 🙏

---

<div class="post-metadata">

**Author:** ![patrickd12345](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/patrickd12345/32/89922_2.png) [@patrickd12345](https://forum.cursor.com/u/patrickd12345)\
**Post date:** [February 28, 2026, 9:37pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/5 "2026-02-28T21:37:46Z")

</div>

same here! Bug report:

Use this report as-is (copy/paste to Cursor forum or support email).

## **Bug Report Draft**

**Title**

Windows renderer OOM crash loop (reason: ‘oom’, code: ‘-536870904’) during normal agent/terminal workflow

**Product / Area**

Cursor IDE (Windows desktop)

**Summary**

Cursor repeatedly crashes with popup:

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

This occurs during normal coding sessions with agent + terminal + browser/debug workflows.

**Environment**

- OS: Windows\_NT x64 10.0.26200

- Repro in recent stable builds (exact build from About Cursor can be pasted here)

- Workspace: medium/large monorepo (web + tests + terminal usage)

- Hardware: (fill in RAM/CPU/GPU)

**Crash Signature**

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

- Frequency: multiple times in a session; can recur after reopen

- Sometimes appears after heavy tool output or long-running agent sessions

**Repro Steps (high confidence)**

1. Open Cursor on a medium/large repo.

2. Run agent tasks that involve:

- terminal commands (type-check/test/dev server),

- browser automation/snapshots/network logs,

- iterative debugging with multiple tool outputs.

1. Continue for ~10–30+ minutes.

2. Cursor crashes with OOM popup.

**Expected**

No renderer crash; stable long-running sessions.

**Actual**

Renderer exits with OOM; active workflow interrupted. Reopen may restore state and crash again later.

**Observed Correlations**

- More likely with high-volume outputs (terminal + browser snapshots/network logs + long chats).

- Reopen with restored editors/session seems to increase recurrence.

**Mitigations that help but do not solve**

- Reopen with **“Don’t restore editors”**.

- Smaller sessions/new chat threads.

- Fewer parallel heavy operations.

- Limiting output volume.

**Impact**

- Blocks ongoing debugging and implementation work.

- Causes repeated context loss and restart overhead.

---

<div class="post-metadata">

**Author:** ![Yair\_Katznelson](https://avatars.discourse-cdn.com/v4/letter/y/9de053/32.png) [@Yair\_Katznelson](https://forum.cursor.com/u/Yair_Katznelson)\
**Post date:** [February 28, 2026, 9:46pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/7 "2026-02-28T21:46:44Z")

</div>

same here

---

<div class="post-metadata">

**Author:** ![Michael\_Ferioli](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@Michael\_Ferioli](https://forum.cursor.com/u/Michael_Ferioli)\
**Post date:** [March 1, 2026, 10:02am UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/8 "2026-03-01T10:02:54Z")

</div>

Same here! I completely rebuilt my entire machine and everything worked fine for about 24 hours and now the problem is back. I am on a Windows 11 machine with 64GB of RAM using WSL with Ubuntu. I’ve been using this configuration for nearly a year with no problems. THIS IS A CURSOR BUG!!! Please resolve it asap!!

---

<div class="post-metadata">

**Author:** ![Yair\_Katznelson](https://avatars.discourse-cdn.com/v4/letter/y/9de053/32.png) [@Yair\_Katznelson](https://forum.cursor.com/u/Yair_Katznelson)\
**Post date:** [March 1, 2026, 4:37pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/11 "2026-03-01T16:37:02Z")

</div>

![Screenshot 2026-03-01 183456](https://us1.discourse-cdn.com/cursor1/original/3X/4/f/4f338f61ecf4fbcfb6fe36580a113f41ac037ea5.jpeg)  
happens again and again, many times and I lose requests!

---

<div class="post-metadata">

**Author:** ![Rob\_devauen](https://avatars.discourse-cdn.com/v4/letter/r/e9c0ed/32.png) [@Rob\_devauen](https://forum.cursor.com/u/Rob_devauen)\
**Post date:** [March 1, 2026, 7:06pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/12 "2026-03-01T19:06:43Z")

</div>

same issue here.. had no problems the first days. Now its happening all the time, no matter what i try to do.

---

<div class="post-metadata">

**Author:** ![Siro\_Buehlmann](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@Siro\_Buehlmann](https://forum.cursor.com/u/Siro_Buehlmann)\
**Post date:** [March 1, 2026, 7:40pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/13 "2026-03-01T19:40:24Z")

</div>

Same problem here! Since 4 days is my cursor not usable anymore. I have to reopen all 2-3 minutes, even though I have enough RAM available. Always the same error message. Even after a re-install: 24h later, I got exactly the same issue. Please resolv it as soon as possible.

---

<div class="post-metadata">

**Author:** ![lolmaxz](https://avatars.discourse-cdn.com/v4/letter/l/dc4da7/32.png) [@lolmaxz](https://forum.cursor.com/u/lolmaxz)\
**Post date:** [March 2, 2026, 8:02am UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/14 "2026-03-02T08:02:07Z")

</div>

Same problem here for the past 2-3 days..  
it’s really annoying because very often it lsoes what just got edited, making rollback complicated, knowing which files got edited or not and AI endeding up with an imcompleted task..  
sometime it even crashes AFTER a prompt and editing was completed.. and yet when restarting, the last message and recap from the prompt is gone anyway.. sometime it even crashes while I’m literally halfway reading the AI’s recap 😕 I hope this gets fixed soon.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [March 2, 2026, 11:13am UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/15 "2026-03-02T11:13:15Z")

</div>

Hi all!

Can you please provide the exact version of Cursor that you’re using, alongside system details ( **Help \> About** or **Cursor \> About Cursor** depending on your system).

---

<div class="post-metadata">

**Author:** ![Landon\_Brown](https://avatars.discourse-cdn.com/v4/letter/l/7ba0ec/32.png) [@Landon\_Brown](https://forum.cursor.com/u/Landon_Brown)\
**Post date:** [March 2, 2026, 11:15am UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/16 "2026-03-02T11:15:04Z")

</div>

same here bro

---

<div class="post-metadata">

**Author:** ![hime](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/hime/32/57286_2.png) [@hime](https://forum.cursor.com/u/hime)\
**Post date:** [March 2, 2026, 12:16pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/17 "2026-03-02T12:16:26Z")

</div>

Hi @Colin this is likely happening due to agent transcript writes (.jsonl), when serializing the json transcript Cursor goes above 4gb in usage and crashes as a result. Tool calls such as subagents also make the OOM happen faster.

This means I often have to start a new chat instead and abandon an old one, once a specific chat causes this. This is also the reason why it keeps repeating for some users, because they’re using an old chat that causes the issue.

---

<div class="post-metadata">

**Author:** ![Peter\_Jaeger](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Peter\_Jaeger](https://forum.cursor.com/u/Peter_Jaeger)\
**Post date:** [March 2, 2026, 7:29pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/18 "2026-03-02T19:29:12Z")

</div>

Same here during every more complex prompt since yesterday:

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/9/a/9a4acb97e8efb183667571d8afe9a4ea3d831c32.png)

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/9/c/9cb86fc5632489b2f84e077b68ef4cf83f9739b5.png)

Super annoying !

---

<div class="post-metadata">

**Author:** ![Paul\_Gibby](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/paul_gibby/32/93433_2.png) [@Paul\_Gibby](https://forum.cursor.com/u/Paul_Gibby)\
**Post date:** [March 3, 2026, 4:24am UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/19 "2026-03-03T04:24:33Z")

</div>

The crash occurs for me when the agent has been running for 3+ minutes, the IDE and chats with agents seem fine until big jobs happen.

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/1/3/13ecd3932567e3239a59906bd56e3ba0192ae4da.png)

I’m using Cursor 2.5.26 system.

---

<div class="post-metadata">

**Author:** ![Daniel\_Havrlant](https://avatars.discourse-cdn.com/v4/letter/d/258eb7/32.png) [@Daniel\_Havrlant](https://forum.cursor.com/u/Daniel_Havrlant)\
**Post date:** [March 4, 2026, 11:58am UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/20 "2026-03-04T11:58:05Z")

</div>

I have the same problem.  
189ac81f-1b99-422a-a0ef-6c58e023587f - reguest ID

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/7/4/74ca313c4602d43c680394c01bd9ae7ea259035c.png)  
I don’t think it’s a lack of memory.

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/5/f/5f4cf28e10d37f4d289c256a4032a244d61a6848.png)

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/9/5/95a44b411b7f0d02917a43699608bd15dd6c0411.png)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [March 4, 2026, 8:13pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/21 "2026-03-04T20:13:09Z")

</div>

Hey all!

We have fixed quite a few memory issues in 2.6, so please try upgrading (you can pull from [https://cursor.com/downloads](https://cursor.com/downloads) if your cilent hasn’t auto-updated)!

---

<div class="post-metadata">

**Author:** ![Zangetsu\_1450](https://avatars.discourse-cdn.com/v4/letter/z/97f17d/32.png) [@Zangetsu\_1450](https://forum.cursor.com/u/Zangetsu_1450)\
**Post date:** [March 4, 2026, 8:44pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/22 "2026-03-04T20:44:37Z")

</div>

Yep, same issue here.

After updating to 2.6.11, I noticed right away that the program was running awfully slow, after a couple of prompts and basic operations RAM usage skyrocketed to 5GB+ (and climbing lol) with CPU usage hovering around 20-30% which points to some sort of memory leak.

Killing the process via task manager and a fresh restart to the welcome window “fixes the issue”, HOWEVER reopening the workspace (that has git history and a couple of active chats with agents) starts leaking memory again, the leak is so severe I can barely get to the built in process explorer without cursor crashing.

Version: 2.6.11 (user setup)  
VSCode Version: 1.105.1  
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990  
Date: 2026-03-03T18:57:48.001Z  
Build Type: Stable  
Release Track: Default  
Electron: 39.6.0  
Chromium: 142.0.7444.265  
Node.js: 22.22.0  
V8: 14.2.231.22-electron.0  
OS: Windows\_NT x64 10.0.19045

 ![cursor memory leak](https://us1.discourse-cdn.com/cursor1/original/3X/3/9/39d79f387484ef98d0b0e4fcfbd4206ac89cf266.png)

---

<div class="post-metadata">

**Author:** ![Yair\_Katznelson](https://avatars.discourse-cdn.com/v4/letter/y/9de053/32.png) [@Yair\_Katznelson](https://forum.cursor.com/u/Yair_Katznelson)\
**Post date:** [March 5, 2026, 8:36am UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/23 "2026-03-05T08:36:07Z")

</div>

Not just annoying, in-progress requests doesn’t get returned.

---

<div class="post-metadata">

**Author:** ![Nick\_Irons](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@Nick\_Irons](https://forum.cursor.com/u/Nick_Irons)\
**Post date:** [March 5, 2026, 9:02am UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/24 "2026-03-05T09:02:41Z")

</div>

![image](https://us1.discourse-cdn.com/cursor1/original/3X/7/5/751328b81596bbfb55e7a760612759a6a25e5ded.png)

I now have the out of memory issue. I didn’t have an issue until cursor updated to 26.11 yesterday. My main project I can no longer work on because cursor closes within a couple of minutes. My backup dev machine has updated itself to the same version and is doing exactly the same thing.

Cursor is very unresponsive now on my other projects when I look at an existing agent chat.

Both pcs, 64gb memory, running nothing else.

I’d like to install the previous build, but the last previous I can see is 2.5

---

<div class="post-metadata">

**Author:** ![kay\_becking](https://avatars.discourse-cdn.com/v4/letter/k/e95f7d/32.png) [@kay\_becking](https://forum.cursor.com/u/kay_becking)\
**Post date:** [March 5, 2026, 12:00pm UTC](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534/25 "2026-03-05T12:00:11Z")

</div>

Same issue! ☹

[Next page](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534.md?page=2)
