For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Hey @XH_ZHENG, you should check your state.vscdb size, this issue seems to happen because yours is way beyond it’s normal limit, create a safe backup and clean this one. If it’s larger than 5 to 8 gb, it should be cleaned up.
it’s stuck because it’s trying to come at peace with all the different cache from the different version, try uninstalling, clearing up residual cache (if that’s ok to you) :
rm -rf ~/Library/Application\ Support/Cursor/*
rm -rf ~/Library/Caches/Cursor
rm -rf ~/Library/Caches/com.cursor
rm -rf ~/Library/Preferences/com.cursor*
and then reinstalling previous version, mhm, if you still want the glass.. i’ll dig deeper into the issue
The node::sqlite::UserDefinedFunction::xDestroy crash at startup is a known low-level issue tied to Cursor 3.x’s new agent runtime + SQLite integration, and it’s particularly stubborn on older Intel hardware.
do you to use the new glass layout or for now you just want a working cursor? if that’s ok to you, for now downgrade to 2.6 seems to be the only path? tho we should wait on some team member to come by figure this out with us
Hey, thanks for the detailed crash log, it really helps. The crash happens in native Electron and Node startup code (node::sqlite::...xDestroy) before the UI shows up, so clearing cache, removing quarantine, or using launch flags won’t help. The issue is below that level. I reported it internally, I can’t share an ETA yet, but I’ll post an update in the thread as soon as I have one.
Why rolling back to 2.6.12 didn’t help: based on your About screen, 2.6.12 uses the same runtime, Node.js 22.22.0 and Electron 39.6.0. The crash is in a module that was added in Node 22, so any version on Node 22 will hit the same problem. To work around it, we need an older build from before the switch to Node 22 and Electron 39.
A couple questions so I can help you pick a working version:
Has Cursor ever launched on this Mac before? If yes, what was the last version that worked?
Can you try an older release, not 2.6.x, but something from before Node 22, and tell me if it starts?
You can find the version list and download links here: Cursor · Download. Grab an older build from there for testing and let me know how it goes.
Hi @deanrie, it seems like from the link you provided, we can get version only up to 3.0, so there is no way to have a pre 2.6 version from there, if you have another link to share, don’t hesitate!
