After asking the AI something, and while it is processing, Cursor crashes and needs to be restarted. After restarting and resending the chat, it crashes again after a while. I can work for a little while, but then it crashes.
Hey, thanks for the report. This is a known issue with crashes caused by OOM on Windows. The renderer process that handles the Agent chat leaks memory over time until it hits the limit and crashes.
A few workarounds that helped other users:
Clear long chat sessions: go to History and delete old or long chats. Long conversations are the main trigger.
Start new chats more often: instead of continuing one long session, open a new thread from time to time.
Delete workspace storage (more drastic): close Cursor, then delete the most recently modified folder in C:\Users\<your_username>\AppData\Roaming\Cursor\User\workspaceStorage.
This will remove all project history, so please back up any important chats first.
The team is aware. Your report helps with prioritization, so I’m adding it to the existing tracking.
Could you also share how much RAM your machine has, and roughly how long your chat sessions usually are before it crashes? That’ll help narrow down the cause.
I asked 18 questions in the chat; I don’t know if that’s what determines the length of the chat. I usually make them much shorter, but that’s how it turned out this time.
It seems that creating a new chat is enough to avoid the OOM problem. But I’m still testing it.
I wanted to let you know that the problem with the size of the globalStorage/state.vscdb file is still unresolved. The file is still growing and now measures 1.1 GB. I don’t know if it will reset at some point or continue to grow, causing problems.
