Cursor becomes unresponsive not long after launching, it shows the dialog with the options to Close, Keep Waiting, Reopen … None of the options fix the issue … It happens always after ~1 min after launch … I tried with a new session in existing project, in “No Repo” , etc.. and no change …
I tried using the AppImage (3.17.19) from Cursor - Download page and the same issue happens … Also my “regular” Cursor is installed via AUR (cursor-bin package) , I tried to run it with the cursor --verbose --enable-logging=stderr command and here is what I got from it …
For now I am using the Cursor 3.15.19 via AppImage to use Cursor IDE but I’d like to be able to use the latest version without an issue …
Please let me know if the issue gets fixed. Otherwise , thanks to the Cursor Team for working hard on fixing issues !
Steps to Reproduce
1- Launch Cursor IDE.
2- New session.
3- Start writing a prompt.
4- Half-way writing the app stop responding and the popup “The window is not responding” shows up.
Hey, thanks for the detailed log. It makes things much clearer.
From what I can see, the window freezes about 40 seconds after startup. At launch, two heavy things kick in. Plugin scanning blocks the main thread twice for about five seconds, and a very large agent session history loads too, around 499 sessions. This time that’s why the window got stuck, it didn’t get far enough to crash.
This looks like the same Linux startup-freeze issue we’re tracking. I noted that it happens both on the AUR package and the official AppImage 3.17.19, and I passed that to the team. For now, please stick with 3.15.19, that one is reliable.
To dig into the root cause, one artifact would really help: a renderer heap snapshot. Here’s how to get it:
Start 3.17.x
About 20 to 30 seconds after launch, before it freezes, open the Command Palette and run Capture and Send Debugging Data
Make sure Renderer heap snapshot is checked, then wait for it to upload
I can’t share an ETA for a fix yet, but I’ll post an update here when I have one.
Thanks for the zip, it’s exactly what we needed. Everything’s clear from it: the freeze reproduces consistently (the window stops responding about 40 seconds after launch), and the capture includes the right trace at the exact moment it hangs. That’s already enough for the team to narrow down where it’s getting stuck on startup, so you don’t need to capture anything again.
About the heap snapshot: it didn’t end up in the archive, but that’s not on you or how you captured the data. It’s on our side. It won’t affect the investigation, the rest of the capture is enough.
This is the Linux startup issue we’re tracking (it showed up around 3.16.17 and continues in 3.17.x). I’ve forwarded your report with the data to the team. I can’t share an ETA yet, but I’ll update this thread when I have news.
For now, please stay on 3.15.19, that’s the right call and it’s stable. Let me know if 3.15.x also starts to lag.
Hey, no news yet. The data you sent is with the team, but I don’t have a status I can share yet. I can’t give an ETA, but as soon as there’s an update, I’ll reply right here.
Thanks for waiting patiently. For now, please stay on 3.15.19, that’s the right choice and it’s stable. If 3.15.x also starts slowing down, let me know.
Hey, good news. The startup freeze you reported, where you get the “The window is not responding” dialog about 40 seconds after launch, is fixed.
The change that caused it was in 3.16, 3.17, and 3.18, so you no longer need to stay on 3.15.19. Please update to the latest 3.19. That should fix the issue on both the AUR package cursor-bin and the official AppImage.
Give it a try and let me know if you still hit the freeze. Thanks again for the debugging data, it helped us find the root cause.
