Generating freeze for every model

Using Cursor 0.46.5 on Macbook Pro M4 Pro 14

Problem seems to happen in remote session like SSH using Open Remote - SSH from jeanp413

No matter which model I use, it’s generating and doing nothing for several minutes and if I Stop and Send again it’s counted in the monthly fast requests quota.

I tried to close and reopen Cursor, didn’t work.

Unusable for now

Hey, check if there are any errors in the DevTools panel.

Same here, 3 hours ago, it was only with Sonnet 3.7, then it moved to 3.5, and now all models. The cursor is collapsing, and I can’t do anything anymore.

Windows on version 0.46.4

Errors in the devtools panel :


Any news regarding this bug ?

Seems critical since I can’t use cursor as his main purpose and every time I try to check if it’s solved it’s 1 more fast request

This is a major problem for me - once it starts happening I have to restart Cursor and then often it will start happening again - using agent mode.

Using .46.4 - and can’t update to more recent version that is out because it fails on windows install - going to stick with .45 for now until these issues are resolved.

poser] Error in AI response: ConnectError: [canceled] This operation was aborted
at vhs.$streamAiConnect (workbench.desktop.main.js:2318:110714)
at async workbench.desktop.main.js:459:133806
at async p_t.toolWrappedStream (workbench.desktop.main.js:965:4404)
at async jC (workbench.desktop.main.js:591:4354)
at async yc.handleStreamComposer (workbench.desktop.main.js:922:2033)
at async vLt.streamResponse (workbench.desktop.main.js:591:13955)
at async dVt. (workbench.desktop.main.js:2976:872)
at async hVt. (workbench.desktop.main.js:2935:2413)
at async GR.processCodeBlocks (workbench.desktop.main.js:948:1926)
at async workbench.desktop.main.js:1918:21531

Still not solved and new error :slight_smile:

I get the same errors and most models stay in the “Generating…” section.

remove the roaming data folder of cursor as something like:
C:\Users\username\AppData\Roaming\cursor

it will completely remove your settings and you will have to start a new conversation etc but it will work as a charm.

i think it happenned because of sending and canceling request before it reached the server, creating a loop of not reaching the server stuck somewhere in the middle.

Since there is no button to purge request or empty cache on the way… this is the fastest solution i can offer.

good luck!

nope it just sometimes freezes like this - its not really cool. Can Cursor take care of this issue?

Found a solution that works for me :

Disable HTTP2 in the settings

Hope this helps !