Cursor on Mac, Apple M1, is crashing every 5 to 10 minutes all day long. Window terminates and reloads, loses some history and then will not restart the chat without a manual /summarize … and then a few minutes later it crashes again!
This is INSANE and not useable at all. This was not happening last week or ever before and now is happening all day long. Nothing changed on my end. I saw it start after the recent updates. I see context filling up very fast in chats (even with max mode off and even when not using a thinking model).
It appears to be a memory leak or some kind of resource contention - or possibly a thinking model issue (thinking tokens might be overloading something?)
…. but it’s a disaster - completely unusable and dangerous as it can lose context of chats and cause errors.
How is this not fixed?
I cannot be the only one with this issue - I searched and see others with it in the past. Why is there no fix from support on this?
I did a reinstall - no luck. This issue is really bad and I would welcome ideas and solutions since the Cursor team seems not to care that their IDE does not work whatsoever for real paying customers at the Ultra tier.
Steps to Reproduce
Use cursor for 10 minutes on a chat with large context 100K+, with Opus 4.5
Crashes every 5 to 10 minutes
Expected Behavior
Don’t crash
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Mine is crashing instantly. It seems to be isolated to a specific workspace where the Agent tab is open. However I cannot verify. I’m trying to figure this out… Not to mention the bug I had a couple of days ago where it automatically starts running code review even though I have that disabled… Using credits and whatnot
awkwardly enough, removing my bun.lock and all node_modules from thee workspaces fixed it.. then i immediately archived all agent conversations as fast as i can as every 5mins i kept getting agent notifications on tasks that were completed days ago.
When the crashes started I was on latest updated version - it began after the update for the visual designer thing Cursor sent out (which I didn’t use - but the instability began immediately after that update)
So I rolled back 2.1 and since then it happened only once instead of every 5 minutes.
Not sure how / if I resolved it here - looks like my install is up-to-date now (I did not actually approve or install updates from 2.1 to 2.2 but it seems to have happened anyway) … but the crashes are not happening (as much) now.
Version: 2.2.20
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z (4 days ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.5.
One thing I noticed while it was happening was that using thinking models (Opus 4.5) the context usage kept filling up very fast - going to 100% in a few minutes - almost like something was thinking constantly and eating tokens in the background. When it reached 80% the crashes would start.
I started using /summarize but that only solved it for a few minutes and then it would happen again.
