Cursor is not usable after the last update

Support Bug Reports
, ,
25

Same on the Mac. Crashes on launch. Tries to load chat then crashes. Unusable.

FIX: Recover from “Crash on Launch” + Observation on Gemini 200k Context Bug

If you are stuck in a crash loop (on Mac) immediately after opening Cursor, the issue is likely a corrupted UI Session State (open tabs/editors) rather than the chat database itself.

The Fix (Mac): Worked for me.

  1. Backup: Go to ~/Library/Application Support/ and rename Cursor to Cursor_Backup.

  2. Verify Binary: Launch Cursor. If it opens as a “fresh install,” your app is fine. Close it.

  3. Restore Workspace:

    • Go to Cursor_Backup/User/workspaceStorage.

    • Find the folder corresponding to your crashing project (sort by Date Modified).

    • Copy that folder into the new ~/Library/Application Support/Cursor/User/workspaceStorage.

  4. The Surgical Fix:

    • Open that specific workspace folder you just copied.

    • Delete the file state.vscdb (This file stores the list of open tabs and UI state).

    • Do NOT delete the other .db files—that is your chat history.

  5. Relaunch: Cursor should now open your project with no tabs open, but your Chat History will be fully intact.

Critical Observation (Possible Root Cause): After fixing the crash and loading the previous chat, I noticed that token usage remained at max (200k+) even after running /summarize.

  • It appears that Manual/Auto summarization is failing to actually release context.

  • This might be causing a “lock” on the model or app state, leading to the crash on next launch.

  • Note: My workspaceStorage folder was under 40MB, so this was not caused by large image assets or file bloat—it seems purely related to token state management.

26

I had to downgrade, clear cache and start a new chat. It’s the end of times here!!!

28

Hey everyone, this looks like a known issue after the latest update. Quick question, what Cursor version are you on?

For now, you can:

Roll back to a previous version Download · Cursor

29

Dean- Rhis has been a problem with EVERY version since I started using Cursor in December.

30

:grinning_face: Come on, this thing is meant to be unstable.

It is a new product that is changing quickly, and I want it to keep changing.

They update fast and they fix things fast.

Clean the machine, install from scratch, and it works.

If not, use something else temporarily.

This whole AI stuff is hit-or-miss. Sometimes you can use it, and then you can’t.

Do the models always give you a 100% super result? No, they don’t. Live with it.

Do your products always work? No they don’t. :wink:

1 Like
31

Yeah, that’s true, but it would actually be nice if the nightly builds had an option to roll back by just 0.0.1, with a background installation, similar to installing a new update. That way, we wouldn’t need to re-download or reinstall the app every time.

I really like 2.5.0-pre15 or pre14. It feels like these versions better prioritize and apply my agentic skills compared to 2.4. This might be subjective, but that’s how i feels in practice.

The dilemma is that I want to stay on 2.5 because I can feel the improvement, yet I end up stuck on an unusable build. At that point, I’m left with two options: either wait for the broken version to be fixed, sacrificing a significant amount of time, sometimes up to a day, or roll back to 2.4, which often results in higher token usage and additional time spent fixing issues it introduces. well overall i really like cursor product with its improvement each minor version update.

32

I was on the latest version so, 2.4.22. I just downgraded to 2.3.1

1 Like
34

This goes back to why cant we get a LTS version? I was finally forced to update from 2.1.42 which I HAD ZERO ISSUES WITH - ZERO! It was amazing never did it hang… never did it stop working… never did I cry myself to sleep.

Now I am on the latest version and cursor fails mid stream, fails connection stream, fails VPN warning error (not using a VPN).

I really would just love a LTS Release… and not feel like a beta tester on each release wasting money on api and subscriptions as a paid subscriber to a product.

1 Like
35

Figured out that cursor is crashing because of an helper services running in the background “Cursor helper (renderer)” which is trying to use more than 100% CPU on my Mac. It’s not the cursor itself but an helper service. Hopefully cursor team has already noticed this

image
image756×302 35.1 KB

36

Crash complete, dont open more after update

image
image2559×1527 19.2 KB

37

lol what a noob team, every update the same bs really fed up

38

To add my $.02, it looks like this is a problem with the extension helper Cursor created custom. Seems like the CPU and memory spikes are just unoptimized parallel execution in the latest update.

It’s definitely not my extensions but rather THE “extension host”… Having 4 helpers for one open workspace is definitely a bug…

39

I confirm, same issue, I analysed locally with cursor I have stuck processes, and coming same time with high token usage of cursor…

40

Yes for the past two weeks or so, Cursor has gotten some extremely dire memory leaks again and it makes it impossible to even type text into the chat box until you restart. I don’t remember it being this bad since about last summer but it’s certainly not the first time this happens.

41

Found this elsewhere, but as reported above it seems to related to the extension host.

I’ve been running latest version from terminal using:

cursor –disable-extensions

Performance is notably improved. Not a long term fix but may help you not need to downgrade til the Cursor team fixes. My Mac’s fans have actually stopped after being on “cool the Sahara" mode for the last 4 weeks.

44

I can confirm that the Surgical Fix works. Had to perform it after the update to 2.4.27