# OOM / Memory Crash on Windows (64GB RAM)

**URL:** <https://forum.cursor.com/t/oom-memory-crash-on-windows-64gb-ram/153773>\
**Category:** Bug Reports\
**Tags:** crashes, windows, performance\
**Created:** [March 6, 2026, 12:26am UTC](https://forum.cursor.com/t/oom-memory-crash-on-windows-64gb-ram/153773 "2026-03-06T00:26:55Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [March 6, 2026, 11:51am UTC](https://forum.cursor.com/t/oom-memory-crash-on-windows-64gb-ram/153773/4 "2026-03-06T11:51:46Z")

</div>

Hey, thanks for the report. This is a known issue on Windows. The Electron renderer process hits a ~4 GB memory limit and crashes, no matter how much RAM your system has. The team is aware and tracking it, but we don’t have an ETA for a fix yet.

For now, here are a few workarounds that have helped other users:

1. Rotate chats: don’t stay in the same chat for long sessions. Once the context gets big, start a new chat.

2. Check for an OTEL leak: open `Ctrl+Shift+P` \> Developer: Toggle Developer Tools \> Console, then look for lines like `[otel.error]` or `OTLPExporterError`. If you see them, that’s a separate memory leak that makes this worse.

3. Monitor memory: `Ctrl+Shift+P` \> Developer: Open Process Explorer. Keep an eye on the renderer process.

Related threads for context:

- [Renderer OOM crash (code -536870904) every ~3 minutes on Windows — 128GB RAM, reproducible](https://forum.cursor.com/t/renderer-oom-crash-code-536870904-every-3-minutes-on-windows-128gb-ram-reproducible/152534)
- [Cursor crashes repeatedly with out-of-memory (OOM) errors after the latest update, especially during large prompts or long-running plans](https://forum.cursor.com/t/cursor-crashes-repeatedly-with-out-of-memory-oom-errors-after-the-latest-update-especially-during-large-prompts-or-long-running-plans/150612)

Let me know if you see any OTEL errors in the console. That will help narrow down the cause.

---

_[View the full topic](https://forum.cursor.com/t/oom-memory-crash-on-windows-64gb-ram/153773)._
