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, thanks for the report. On 3.1, OOM cases have become rare, so I’d like to look into your case separately.
To dig deeper, I need a few things:
Crash and renderer logs: open Help > Toggle Developer Tools > Console before the crash if you can reproduce it, then send a screenshot or paste the errors. This also helps: Help > Show Logs > Renderer log.
The Request ID for the last request to Composer before the crash if Privacy Mode is off: in the chat top right corner > Copy Request ID.
Session context: what was the prompt or task, how many files were in @context, whether you edited a large file, and how long the session ran before the review indicator spike.
Project size roughly, and whether any MCP servers are active.
If you can reproduce it: Ctrl+Shift+P > Developer: Open Process Explorer and send a screenshot of process memory right before it crashes.
The symptom where the review indicator jumps to an unreal number is familiar. It looks like it might be keeping full file contents in the review state during large edits. With your details, I can tie it to a specific internal issue.
