Window Unresponsive When Generating Reply

Bug Reports
1

Recently Cursor was getting more and more sluggish as soon as it started generating a response, to the point where the window became unresponsive until the reply was fully generated. Also the whole process from prompt to reply was a fair bit slower than I was used to. I read here and there that it may be related to chat history. I noticed in the AppData\Roaming\Cursor\User\globalStorage the state.vscdb file had grown to 1.5 gigs. So I removed it and after having to sign back into cursor and putting my settings back to how I had them it works very quick and smooth again.

Not an ideal process to go through, but it worked. It was like it was trying to read this entire 1.5 gig file every time! I’m curious what information is stored in that file for it to grow that large.

Hopefully it’s something that can be addressed in a future update.

Windows 11
0.49

2

This file stores all the settings and data of the Cursor. Actually, you could just try renaming your project or moving it to another location on your disk, and that would solve the problem.

You could also try clearing the folder AppData\Roaming\Cursor\User\workspaceStorage where all the history of your projects is stored. This would also solve your problem.

1 Like
3

Does the size of the state.vscdb file seem normal to you? I am wondering if it’s suggesting a faulty extension which may have somehow caused this bloat.

Or am I just completely off track here and just simply removing the history would do the trick and the state.vscdb is normal at 1.5 gigs and not effecting things negatively?

4

Actually, this is not a normal size for this file. The reasons can vary, and some of them might be:

  • Some extensions save a large amount of data
  • Lack of automatic cache cleaning
  • Large datasets for IntelliSense and auto-completion
  • Workspaces and related data
  • Error logs that are not deleted over time
  • Global state data that extensions save through the globalState API

cc @danperks

5

Thank you for all your replies.

So I put my question to deepseek and gpt, they suggested looking at the state.vscdb file with DB Browser for SQLite. So I opened my current state.vscdb file and sent a screenshot off to gpt and deepseek and they both flagged the cursorDiskKV table as a red flag.

deepseek:

Potential Issue Summary:
The state.vscdb file shows schema corruption (invalid SQL syntax) and an unexpected table cursorDiskXY, indicating possible database corruption or unintended modifications. Combined with prior extreme bloat (1.5 GB), this suggests:

  1. Cursor/Extension Bug: Faulty logic writing invalid data.
  2. File Corruption: From crashes or incomplete writes.
  3. Misbehaving Extension: Creating non-standard tables or spamming entries.

Action: Report the schema anomalies to Cursor’s support team for investigation.

I don’t have the expertise to say how accurate this is, but it’s intresting that both gpt and deepseek pointed out the same cursorDiskXY as being a red flag!