Severe performance issues with Cursor 0.45.9: Running slowly, freezing frequently, and not updating files

The problem of Cursor running slowly started after I updated it to version 0.45.9. It begins shortly after Cursor initializes and persists throughout its use, making it almost impossible to use at times. Even when I manage to use it, Claude often doesn’t effectively modify the content of the files, and I end up having to ask it to show me the complete code so I can copy and paste it.
However, I’ve been experiencing this issue with Claude even before the update.

@danperks Do you have any idea about how to solve this issue?

Hey, does this happen even if Cursor is not opened to a folder, and is just sitting idle?

are you using multiple agents?

@danperks Hi, I’ve just tested it, and Cursor works smoothly when it’s not opened to a folder. Then I opened a project different from the one where the issues started, and I didn’t notice any problems there either. However, when I returned to the original project, Cursor started running slowly and freezing again.

It freezes even when I’m not using Composer—for example, when switching tabs or opening files. It also takes a long time to create new files or folders.

What can I do to fix this?

@lulavc I don’t think so. These issues happen even when I’m using the normal mode instead of agents mode, and they occur even if I’m not using Composer at all.

By the way, I’ve never heard of the multiple agents feature before. Could you please elaborate on how it works and how to activate or deactivate it?

I’m using Linux version I noticed it updated itself from

cursor-0.45.8-build-250201b44xw1x2k-x86_64.AppImage

to

cursor-0.45.9-build-250202tgstl42dt-x86_64.AppImage

I caught it in the act a day ago and swapped it back to 045.8 since 0.45.9 messed up my local file structure and re-wrote directories from the repo root instead of the ./present-working-directory

This caused hours of confusion until I figured it out, reverted back to 0-45.8 and tried to keep an eye on it. Happened again in the middle of a huge session, no warning.

0.45.9 does not seem to be a healthy build and it seems that 0.45.8 has an aggressive update strategy on Linux.

In summary

  • 0.45.8 auto updated even when I said no to the popup on the bottom

  • The first time I intentionally updated from 0.45.8 and found out 0.45.9 is not a good build and reverted.

  • Second time it auto updated when I simply clicked on “read change log”.

  • Third time it auto updated without me touching the “Update Cursor” panel.

  • Since I had been burned twice I knew to keep an eye on the update and not to trust it. But, when I restarted Cursor I noticed it had replaced itself (since my symbolic ~/bin/cursor app failed).

  • Had I not restarted I would have drilled another session into the void due to it auto updating from 0.45.8 to 0.45.9.

My solution is to go to the main website and download from the main “DOWNLOAD” link which has always been 0.45.8 during this time of oddness. I now keep an hidden backup of 0.45.8 so that when the system replaces itself with the errant build, I can subvert it.

This requires me keeping an eye on things way more than I would like, of course.

Cursor is an amazing tool and but this bug is not sparking joy or confidence atm. Thanks, good luck fixing and refining.

The first time 0.45.9 was being installed in my OS (Windows 11) it triggered a BSOD. Then I installed the previous version but it was updated again.

1 Like

Hey, can you give 0.45.10 a go when you are able to accept the update, as both in 0.45.10 and the upcoming 0.45.11, we have a ton of performance increases!

@danperks Thanks! Version 0.45.10 is working much better. Freezes are now rare, and when they do happen, restarting Cursor usually fixes the issue. Hopefully, version 0.45.11 will fully resolve the performance problems.