I don’t know how to repro it, but the crash happens over 20 times a day I think? The window shows
" The window terminated unexpectedly (reason: ‘crashed’, code: ‘5’)
We are sorry for the inconvenience. You can reopen the window to continue where you left off.
"
Thanks for reporting a bug you have found in Cursor!
Please add the following info to help us diagnose your issue:
Check the forum to ensure the issue hasn’t been reported already Provide a clear description of the bug Explain how to reproduce the bug (if known) Attach screenshots or recordings (e.g., .jpg, .png, .mp4). Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x). Tell us if the issue stops you from using Cursor.
it should be fixed in 0.47, i updated cursor and it did fixed at the beginning, at least i can use the send button. But sometimes i still can’t type in the composer. The case happens when i add a folder at the end of the composer like it
I guess it’s the long chat history cause the issue. After I uninstall and re-download cursor, the default chat will change to be empty and I can use it normally. But before i uninstall it, i tried to delete the chat history, it will first show i delete successfully but then crash, and after i reopen it, the history will come back and i can’t use cursor again.
So the key point is to delete the long chat history by uninstall and redownload it
Hey, you can rename your project to make all your chat history disappear. However, I recommend just keeping an eye on its size and periodically deleting the unnecessary ones. Also, if your chat history is important to you, you can save it to markdown files using this extension:
Since i updated (i didn’t want to) to version 0.47.5, it keeps on crashing every 10mn or so… I used to work on the 0.45.17 and I never has that crash where everything closes and I just have the option to reopen… Very annoying, a big downgrade
Hi, if you’re on non-privacy mode, could you run cmd+shift+p → Developer: Capture and Send Debugging Data and let me know when you’ve ran it? I can investigate the logs and debug data to see what’s wrong here.
If you could also run cmd+shift+p → developer: Toggle Watch for Crashes when starting up the editor that be helpful; that will similarly send some debug data right before a crash so we can investigate what’s wrong and fix it. (cmd+shift+p` -> `developer: Toggle Watch for Crashes has to be ran after opening the editor each time)