Every time I try to run a chat it gets stuck for a while, and then after that all of Cursor crashes. This is getting really frustrating because now I don’t have any way to do my work with the chat assistance, which is the only reason I am paying for this program. It has repeatedly blocked me from operating git through the IDE and I have lost access to typing in the terminal as well. This is very frustrating because I have an important deadline coming up and I need to at least be able to work on my code manually even if I am not using the chat functionality and even that is blocked. Oh and I apparently can’t use the top menu to find out what version this is either. Or exit the app without killing it from the control panel. This is ridiculous. I am using Composer1 and have the pro+ plan on Windows 11.
Steps to Reproduce
Just working normally and asking the chat anything.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
I don’t know why this is saying that I was on version 2.1 because when I checked again I was on version 2.3. After digging around online I was able to find that 2.3 is likely the culprit so I downgraded to 2.2.244. I will let you know if this helps in any way, as of right now the whole interface is slow as heck.
I kind of got chat working again if I only used it in Ask mode, that is until it just decided to completely crash with no warning, no explanation. This has been the most frustrating day of work in a long time and I would really appreciate any help from the Cursor team because I have deadlines to meet and it’s your product that is screwing me over. It would be one thing if just the part I am paying for is not working (the Agent/Ask functionality) but it’s another to have my code editor not even let me write code since it’s constantly crashing. If this doesn’t get fixed in the next day or so I am asking for a refund and having my team move to a different product.
Hi @Nathan_Rensing and sorry to hear about your issue with Cursor. This should not happen though we may need more information in order to determine cause and see what needs improvements.
Could you check following and provide more info?
Request ID’s where things do not work, alternatively a screenshot.
Check your computer resources: how much memory/CPU does Cursor consume compared to your total?
Check also Help > Open Process Explorer and share a screenshot of what processes consume most memory or CPU as it may be an indication if extensions, or other features like language server as well as long running terminal processes may consume resources.
Check Settings > Network and Run Diagnostics, then post here any errors shown there.
Also in Help > Toggle Developer Tools, then open Console and paste any errors shown there here.
That info should help us to see what is causing the issue in your case.
I don’t know how to get you the request IDs when it freezes because I literally cannot click on anything to get information, I had to restart it to just get the version number to bring up this issue.
Resources wise, it does look like its hitting about 70% on CPU at some points and 50% on memory but nothing further and its usually sitting around 20% CPU while frozen.
Again for this I can’t actually access the menus when its frozen so I don’t know how I would get you that information.
In case it helps, the way I use cursor is through windows, however I am sshing into a server through my companies’ vpn.
workbench.desktop.main.js:13199 [Background Composer] Error updating branch on git status change: Error: No full commit provider registered at iss.getCurrentBranch (workbench.desktop.main.js:542:342094) at zLt.value (workbench.desktop.main.js:13199:53537) at Ee._deliver (workbench.desktop.main.js:49:2962) at Ee._deliverQueue (workbench.desktop.main.js:49:3053) at Ee.fire (workbench.desktop.main.js:49:3390) at dqc.$gitStatusWasRun (workbench.desktop.main.js:12365:35951) at xBo._doInvokeHandler (workbench.desktop.main.js:13027:22831) at xBo._invokeHandler (workbench.desktop.main.js:13027:22573) at xBo._receiveRequest (workbench.desktop.main.js:13027:21335) at xBo._receiveOneMessage (workbench.desktop.main.js:13027:20152) at zLt.value (workbench.desktop.main.js:13027:18244) at Ee._deliver (workbench.desktop.main.js:49:2962) at Ee.fire (workbench.desktop.main.js:49:3283) at Tvt.fire (workbench.desktop.main.js:12360:12156) at gmf._receiveMessage (workbench.desktop.main.js:12360:17134) at zLt.value (workbench.desktop.main.js:12360:14485) at Ee._deliver (workbench.desktop.main.js:49:2962) at Ee.fire (workbench.desktop.main.js:49:3283) at Eao.acceptChunk (workbench.desktop.main.js:12360:9029) at workbench.desktop.main.js:12360:8157 at zLt.value (workbench.desktop.main.js:14986:125721) at Ee._deliver (workbench.desktop.main.js:49:2962) at Ee.fire (workbench.desktop.main.js:49:3283) at Ppm._fileReader.onload (workbench.desktop.main.js:14986:123985) (anonymous) @ workbench.desktop.main.js:13199 workbench.desktop.main.js:13074 [transport] Connect error in unary AI connect ConnectError: [unauthenticated] You must be a team member to access this resource at t (workbench.desktop.main.js:12375:457550) at async Object.getTeamCommands (workbench.desktop.main.js:585:88139) at async vMo.loadTeamCommands (workbench.desktop.main.js:15030:2986) Object error @ workbench.desktop.main.js:13074 workbench.desktop.main.js:15030 Failed to load team commands: ConnectError: [unauthenticated] You must be a team member to access this resource at t (workbench.desktop.main.js:12375:457550) at async Object.getTeamCommands (workbench.desktop.main.js:585:88139) at async vMo.loadTeamCommands (workbench.desktop.main.js:15030:2986) loadTeamCommands @ workbench.desktop.main.js:15030 workbench.desktop.main.js:13074 [transport] Connect error in unary AI connect ConnectError: [invalid_argument] Error at t (workbench.desktop.main.js:12375:457550) at async Object.getGithubAccessTokenForRepos (workbench.desktop.main.js:585:88139) at async Uut (workbench.desktop.main.js:585:82370) at async u (workbench.desktop.main.js:15042:22121) Object error @ workbench.desktop.main.js:13074 workbench.desktop.main.js:55 ERR [Extension Host] [otel.error] {“stack”:“OTLPExporterError: Bad Request\n\tat IncomingMessage. (/home/nrensing/.cursor-server/bin/20adc1003928b0f1b99305dbaf845656ff81f5d0/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:52:31)\n\tat IncomingMessage.emit (node:events:530:35)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:82:21)”,“message”:“Bad Request”,“code”:“400”,“name”:“OTLPExporterError”,“data”:“{"error":"Trace spans collection is disabled for NO_STORAGE privacy mode"}”} error @ workbench.desktop.main.js:55 workbench.desktop.main.js:12343 [Extension Host] [otel.error] {“stack”:“OTLPExporterError: Bad Request\n\tat IncomingMessage. (/home/nrensing/.cursor-server/bin/20adc1003928b0f1b99305dbaf845656ff81f5d0/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:52:31)\n\tat IncomingMessage.emit (node:events:530:35)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:82:21)”,“message”:“Bad Request”,“code”:“400”,“name”:“OTLPExporterError”,“data”:“{"error":"Trace spans collection is disabled for NO_STORAGE privacy mode"}”}
hi @Nathan_Rensing. we apologize for the inconvenience. do you have git installed on your machine? we’re aware of a bug where not having a reachable git installation causes the agent to break and/or get stuck. if so, this bug has been fixed in a version that is getting rolled out over the next day or two.
I don’t have git installed on the windows machine that I am working from, however that is because all of my work is done through SSH to a Linux server which does have git on it.
Today I was not running into the problems that I ran into yesterday despite not having changed anything on my end. I am sure that the problem still exists and will likely come to haunt me again but for today at least I was able to get work done.
In the case where it freezes, how do I get diagnostic information that I can provide to you if I can’t access any of the menus?
I see, thank you for the information. If you run into this again, it would be great if you get us a log export. from the command palette (ctrl/cmd-shift-p) you can run > Developer: Export Logs… and select Window, Main, Extension Host, Extension Host (Remote) (if available), Remote - SSH.
