Thanks for the logs, they’re really informative. They show two clear issues:
-
SQLite concurrency bug: Your logs are flooded with
AgentAnalyticsOperationsMainService: SQLITE_ERROR: cannot start a transaction within a transaction, hundreds of times between 16:12 and 16:18. This is a known issue where the analytics service gets stuck in a loop of failed DB writes, which eats CPU and memory. -
Bloated local database: The logs show
DB size: 5860462592b, that’s about 5,8 GB for a local storage file that should be small. One key alone,aiCodeTrackingLines, is 3,1 MB. This causes about a 7 second delay just to close the DB, and it almost certainly contributes to freezes and rising memory use.
Here’s what I’d suggest:
- Fully close Cursor
- Go to
%APPDATA%\Cursor\User\globalStorage - Find the folder that contains
state.vscdband check its size. If it’s a few GB, deletestate.vscdband also anystate.vscdb.backuporstate.vscdb.corrupted.*files - Restart Cursor (you’ll lose some local state, but this should fix the bloat)
For the future:
- Fully restart Cursor (quit and relaunch) every 1 to 2 hours during long sessions
- Start new chats instead of endlessly continuing very long ones
The team is aware of the SQLite transaction issue. Your logs are very helpful as extra evidence. Let me know how it goes after clearing the database.