Cursor 0.47.8 (Linux version) can not startup and CPU 100%

Bug Reports
1 
cursor --version
0.47.8
82ef0f61c01d079d1b7e5ab04d88499d5af500e0
x64

maybe related error log (from window2/renderer.log and window1/renderer.log) :

[error] Maximum call stack size exceeded: RangeError: Maximum call stack size exceeded
at Co.shouldWaitFor10SecondsWhileReadingFromDiskAtStartup [as resetComposers] (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:596:10680)

[b00] potential listener LEAK detected, having 5484 listeners already. MOST frequent listener (5369):: Error

open a project which has 6w LOC:

UI no response

Chat side window showing “Loading Chat”

I can confirm that open tiny small project just works.

image
image1334×1181 42.4 KB

image
image990×556 25 KB

2

others got 100% cpu too: Cpu problem after last update

3

Hey, I think in your case the problem is related to a large amount of history in your chats. Try opening an empty project and see if that solves the problem. If it does, try renaming your project to clear the history.

6

I can confirm that, I do not have a large amount of history in my chat in this project.

I hardly ever open this project.

another thing I can confirm is: rename the fold will make Cursor startup succeed.

I can say with great certainty that this version of Cursor should have this bug; it should be said that the recent few versions all have it. You need to fix this issue.

1 Like
7

I’m also experiencing this issue, after updating from 0.46 to 0.47, the program doesn’t load.
I did manage to get it to load once after a very long weight, but in general it’s not working.
I have rolled back to 0.46, and that is working fine.

8

I’m experiencing this now as well on Fedora after upgrading to v0.47.9. Most of my chat histories are not that long, and most of the codebases in question are <5000 lines. Yet this issue seems to apply to all of my projects with any chat history at all (a couple dozen at this point). The project I first noticed this with, I think the only AI request I even made was one inline request with Cmd-K asking it to refactor one function. These projects previously opened just fine with very little delay, and definitely not a crash.

Given the number of projects and that I have the directories set up how I want, renaming all of them is not ideal. I have indeed mitigated this by simply deleting the workspace caches (which for the AppImage are located at ~/.config/Cursor/User/workspaceStorage/*) but again, not ideal to lose all that history.