Cursor crashes repeatedly with out-of-memory (OOM) errors after the latest update, especially during large prompts or long-running plans

Support Bug Reports
, ,
54

Definitely fixed for me. I’ve probably used Cursor for 12 hours since installing the latest version. Zero crashes. Previously, I experienced a memory leak-related crash every five minutes or so.

1 Like
55

I got desperate and started trying nightly yesterday, didn’t help. 64 crashes trying to get some work done.

Took update today, and we’r eon 6th crash in like 20 minutes.

Version: 2.6.0-pre.33.patch.0 (user setup)
VSCode Version: 1.105.1
Commit: 3a1ff150ed66f295af45ae38f28f6afaa05a4770
Date: 2026-02-23T23:34:26.530Z
Build Type: Stable
Release Track: Nightly
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26300

2 Likes
56

Our company teams are also affected, several crashes per hour, despite the fact the crashes are very annoying, continuing always consumes extra requests. So it’s also about money. TbH, i don’t want to see anything else before this issue is fixed. Previous versions hat their flaws, but did their job without crashes.

Sorry to say so, because i like cursor, but in this state, abandoning cursor and cancelling our contracts is on the table. :disappointed_face:

1 Like
57

Yup same problems here .. has been driving me crazy and yes i agree with comments about wasted time and wasted tokens and expense … is very frustrating .. win11 96GB RAM rtx5070ti on an external GPU host …. how can 96 GBRAM and 16GB VRAM not be enough … “DAMN YOU MICROSOFT !!!”” said in a colonel clink kind of hogans heroes voice !!! …….. To be honest I wonder if they even care about this at microsoft as they are so busy creating slop for their windows for extra fat profits …. It would be nice to know when this and if this is going to be resolved .. its a headache to the MAX .. I jam quite new to cursor and have just subscribed for the 12 month pro plan up front .. I have been really happy with things until the OOM crashes started .. I have now reduced my file overheads in the window to a minimum and still I get them .. damn annoying .. should i stay and will it be fixed ?

60

So a month later and still no solution to this issue ? well I suppose is time to look on alternatives and stop wasting time and money here.

62

Hi Cursor team - your product is amazing but please fix this, we are an enterprise customer and cannot run basic generation tasks, the OOM happens after just a few mins, this was not happening prior and the team is stalling. This is urgent from my view and makes the product unusable. Thank you

1 Like
63

I asked Cursor to patch the Otel related failure . let’s see

Here’s what the patch does across all 3 variants (src, esnext, esm):

What changed: The export() method in OTLPExporterBase now immediately calls back with { code: 0 } (which means ExportResultCode.SUCCESS) and returns, instead of forwarding to the delegate that tries to HTTP POST to Cursor’s backend. No network call is ever made.

Backups created:

  • OTLPExporterBase.js.bak in build/src/, build/esnext/, and build/esm/

don’t mind doing it after every update if it takes care of the OOM thingie .. the whole point is to run for hours