After querying the Cursor agent (Composer 2), the review indicator (green numbers of line changes) jumps into unrealistic number and IDE stops responding, now when I click option to reopen, it opens it up, while starting up, it stops responding again.
Getting error: reason: ‘oom’, code:‘-536870904’
Steps to Reproduce
Query composer to do some task (plan, agent), the review number spikes and IDE stops responding
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
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.
