@Dave_Howson, ok, the symptoms changed. If an empty window opens but a specific workspace freezes the IDE, then it’s not the global state.vscdb. It’s workspace specific storage. Each workspace stores its state in ~/Library/Application Support/Cursor/User/workspaceStorage/<hash>/, and it can grow on its own. This is a known pattern with bloat in workbench.find.history and cursorDiskKV.
Try this step by step, don’t wipe everything:
- Run this to find large workspace folders:
du -sh ~/Library/Application\ Support/Cursor/User/workspaceStorage/* | sort -h | tail -20
If something is in the hundreds of MB or in GB, that’s a good candidate.
- Match the hash to your workspace using the
workspace.jsonfile inside that folder:
cat ~/Library/Application\ Support/Cursor/User/workspaceStorage/<hash>/workspace.json
- Once you find the right workspace, rename the folder, don’t delete it:
mv ~/Library/Application\ Support/Cursor/User/workspaceStorage/<hash> ~/Library/Application\ Support/Cursor/User/workspaceStorage/<hash>.bak
Open the workspace again. Cursor will create a fresh folder.
- If the workspace freezes again after some time, grab two
main.logfiles during the freeze, one from just before and one from just after, from the newest folder in~/Library/Application Support/Cursor/logs/. Those logs usually show what the startup is getting stuck on.
No ETA on a real fix for the bloat yet, but locally this keeps the workspace usable without doing a full wipe.