Is anyone else noticing the Cursor IDE randomly closing itself without warning?

Discussion
1

Not sure if it’s my system or some weirdness at my end, or a bug in Cursor, but the entire window just vanishes on me, maybe 4 or 5 times per day? Been doing that since 0.46 dropped, in Windows 10 and Windows 11.

Just did it right now, as I was in the middle of typing a sentence in there.

2

Looked in the logs. This might be the cause?

TimeCreated : 7/03/2025 3:53:57 PM
Id : 1000
LevelDisplayName : Error
Message : Faulting application name: inno_updater.exe, version: 0.0.0.0, time stamp: 0x67b2cf1c
Faulting module name: inno_updater.exe, version: 0.0.0.0, time stamp: 0x67b2cf1c
Exception code: 0xc0000409
Fault offset: 0x000000000004a549
Faulting process id: 0x15B8
Faulting application start time: 0x1DB8F254CF0F1BB
Faulting application path: C:\Users\cnd\AppData\Local\Programs\cursor\tools\inno_updater.exe
Faulting module path: C:\Users\cnd\AppData\Local\Programs\cursor\tools\inno_updater.exe
Report Id: d974a351-a710-44ab-beb9-bc6586c29ab8
Faulting package full name:
Faulting package-relative application ID:

3

Hey, it seems the issue is related to an update. Cursor tries to update and closes for this. Try downloading the latest version here:

Also, we will try to fix this error in the future.

1 Like
4

I’m on .47.5 and it is randomly closing down as much as possible

Also still having significant cursor slowdown when using the agent mode with high cpu that freezes cursor for a few seconds often. I think the cause is a longer agent chat (but sometimes want to keep it going until the current task is completed) or the number of Edited files above the chat box becoming too large.

5
6

Appreciate the reply. There are two issues going on here.

  1. The random closing itself without warning. I personally never saw this before .47.5, even when not experiencing the chat cpu.
  2. The chat cpu usage which you said was related to chat history. Not sure why it makes sense to delete all chat histories, but I see your point. Usually just opening a new agent chat solves it for awhile so that would support your thoughts. But that then takes more work to familiarize the new agent with codebase, patterns, etc. Even with extensive ruleset, my experience is that you have to refocus the new agent. And then takes more tweaking. There is not great memory between chats even on the same model imho. On the plus side, the new agent chat is usually more on point once you spend the time to give it context again.

Again, really appreciate your reply!
Jeff

1 Like