# Cursor stops responding, after reopen, it stops again

**URL:** <https://forum.cursor.com/t/cursor-stops-responding-after-reopen-it-stops-again/158546>\
**Category:** Bug Reports\
**Tags:** crashes, performance, composer, review\
**Created:** [April 20, 2026, 6:56pm UTC](https://forum.cursor.com/t/cursor-stops-responding-after-reopen-it-stops-again/158546 "2026-04-20T18:56:33Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [April 20, 2026, 7:11pm UTC](https://forum.cursor.com/t/cursor-stops-responding-after-reopen-it-stops-again/158546/5 "2026-04-20T19:11:45Z")

</div>

Hey, this is a known issue, renderer OOM `-536870904` on Windows. It’s usually triggered by large Composer diffs. It’s on our side and we’re tracking it, but I can’t share an ETA for a fix yet.

The crash loop on restart happens because the bloated Composer state gets reloaded from the database and immediately eats the V8 heap. A few workarounds that have helped other users:

- When reopening after a crash, choose Don’t restore editors, or disable restore in `settings.json` via `"window.restoreWindows": "none"`
- Start a new chat instead of continuing the broken one, so the old state won’t be pulled in
- Avoid turns where the agent loads lots of files into context and also does a big write. Split the task into smaller chunks

Main thread with reports and discussion, follow for updates: [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)

To help us pin down your case, please share the full output from Help \> About, we need the Electron, Chromium, and V8 versions, plus how much RAM your machine has. If you can catch it right before the crash, a screenshot from Process Explorer `Ctrl+Shift+P` then Developer: Open Process Explorer showing renderer memory usage would help a lot.

---

_[View the full topic](https://forum.cursor.com/t/cursor-stops-responding-after-reopen-it-stops-again/158546)._
