After a long time of using Cursor, I’ve noticed that focusing/unfocusing the window has become very slow. At the same time, closing the editor triggers a popup with “Saving UX state” message, which takes a couple of seconds. I’ve managed to narrow it down to globalStorage folder being too large, after deleting it ($HOME/.config/Cursor/globalStorage) and reconfiguring Cursor again, the UI feels much faster.
Steps to Reproduce
Have a large Cursor config.
Unfocus the window.
Refocus and notice that tabs are not clicking and you can’t type.
Expected Behavior
Fast and furious UI.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Hi @heraldev thank you for the update. Have you already upgraded Cursor to 1.2.4 as that version has had performance updates?
If the UI issue continues after upgrade please check following:
When UI freezes, does Cursor consume a lot of memory or CPU? If yes, please post a screenshot of Help > Open Process Explorer to see what is happening there.
Use Developer: Open Logs Folder in command palette and check for errors there
Check Help > Developer Tools > Console and report errors shown there.
Check what folders or files in $HOME/.config/Cursor/globalStorage are getting large, any db file or extensions subfolder?
You mentioned Have a large Cursor config, what settings are large or is that the Cursor globalStorage folder?
There are further improvements already in progress but I would need to check if yours are related or another issue altogether.
The folders are small, I would expect performance issues at GB folder sizes.
Process explorer:
Shows no CPU load
RAM usage shows somewhat larger usage for
Next-server: Does handling improve if you restart npm run dev?
Ai-agents.ts: Is the ts file large? (approx. lines of code)
BG agent: if you merged the background agents code, you can delete the background agent, it would free up also more memory.
Question: what is your total RAM on this device? and how much does Cursor use?
Disable all extensions temporarily: Run cursor --disable-extensions from the command line. If issues resolve, re-enable extensions one by one to identify the problematic one.