Solved: the reason why Cursor keeps crashing

Bug Reports
1

specstory.

The extension specstory opens and reads the Cursor sqlite files, and if Cursor itself happens to need to read/write those same files at the same time - it cannot - so spits out this error and exits:

2025-04-19 17:04:03.013 [error] [storage state.vscdb] transaction(): Error: SQLITE_BUSY: database is locked
2025-04-19 17:04:03.028 [error] [uncaught exception in main]: Error: SQLITE_BUSY: database is locked SQLITE_BUSY: database is locked

To confirm for yourself this is the reason for you - look in %APPDATA%\Cursor\logs for the most recent folder, and inspect the “main.log” file in there…

3 Likes
2

Life-saver!! So lucky you posted this 8hr ago, these crashes have been very disruptive.

3

@gregce

4

We’re troubleshooting this here: Is this the cause of Cursor suddenly closing without warning? · Issue #54 · specstoryai/getspecstory · GitHub and have not been able to repro the issue yet despite these reports. Thank you @deanrie

5

What about my case, my cursor it’s frezing

2025-04-24 14:26:18.387 [info] updateURL https://api2.cursor.sh/updates/api/update/win32-x64-user/cursor/0.49.4/e3136ee2440c75f295c6e435299d11666f9c1ee9d60d992e3ff54f6d92026b89/stable
2025-04-24 14:26:18.387 [info] update#setState idle
2025-04-24 14:26:48.862 [info] update#setState checking for updates
2025-04-24 14:26:49.240 [info] update#setState idle
2025-04-24 14:26:50.809 [info] Extension host with pid 18160 exited with code: 0, signal: unknown.
2025-04-24 14:28:13.876 [error] CodeWindow: detected unresponsive
2025-04-24 14:28:17.403 [info] Extension host with pid 924 exited with code: 0, signal: unknown.
2025-04-24 14:43:40.617 [error] CodeWindow: detected unresponsive
2025-04-24 14:43:48.471 [info] Extension host with pid 25340 exited with code: 0, signal: unknown.
2025-04-24 14:46:57.694 [error] CodeWindow: detected unresponsive
2025-04-24 14:47:17.101 [info] Extension host with pid 6824 exited with code: 0, signal: unknown.
2025-04-24 14:48:39.927 [error] CodeWindow: detected unresponsive
2025-04-24 14:48:42.215 [info] Extension host with pid 25572 exited with code: 0, signal: unknown.

6

@gitcnd others: we just got to the root of the bug affecting some and were able to reproduce it and fix it. Thanks much @gitcnd for helping to sniff out a scenario we could finally repro!

The newest release 0.11.3 as of this morning fixes it.

The release takes a bit to populate to the Extension Marketplace in Cursor, in the meantime, you can download and install the VSIX from either: Open VSX Registry or Install the extension - SpecStory

Steps to reproduce on 0.11.2 and before running Cursor 0.49.6 (which are likely somewhat dependent on machine resources but I was able to repro consistently with a M4 Pro and 48gb of ram which is quite beefy). Others with less specc’ed machines might have experienced this with different below permutations.

  • Have auto-save in SpecStory turned on in settings
  • Have a state.vscdb in globalStorage that exceeds 500MB (mine for reference is ~800MB+)
  • Have a mix of v2 and v3 composerData in said state.vscdb
  • Open 8+ Cursor windows for projects simultaneously. I did this by turning off auto-save opening up the windows, turning on auto-save and force quitting Cursor so it would remember the workspace window sate.
  • On startup when SpecStory activates and Cursor runs its initial processes after ~30 seconds it will crash

The fix was ultimately quite simple in terms of delaying an initial autosave attempt on startup and letting the polling process work normally.

Finally, even in 0.11.2 and before if you opened 1 or 2 Cursor windows with auto-save on it would not crash which made it difficult to trace the root cause.

7

I’m still getting crashes on launch. Just installed for first time today.

Identifier

specstory.specstory-vscode

Version

0.11.3

Last Updated

2025-05-01, 13:58:28

Size
494.0 KB

Not sure where my log files are…

8

Would it be possible for you to provide some more details in a bug report here?
specifically around OS, etc. Also, are you just opening Cursor normally?

9

agree Built a Cursor Extension to save and share chat and composer history - #34 by krstoevan

10

Your latest release seems to have fixed it from what I can see, good stuff.

1 Like