# Window Unresponsive When Generating Reply

**URL:** <https://forum.cursor.com/t/window-unresponsive-when-generating-reply/86346>\
**Category:** Bug Reports\
**Created:** [May 4, 2025, 4:56pm UTC](https://forum.cursor.com/t/window-unresponsive-when-generating-reply/86346 "2025-05-04T16:56:56Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![MTNBys](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mtnbys/32/51693_2.png) [@MTNBys](https://forum.cursor.com/u/MTNBys)\
**Post date:** [May 4, 2025, 7:24pm UTC](https://forum.cursor.com/t/window-unresponsive-when-generating-reply/86346/5 "2025-05-04T19:24:53Z")

</div>

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!

---

_[View the full topic](https://forum.cursor.com/t/window-unresponsive-when-generating-reply/86346)._