hi @Work_Dre, thanks for taking the time to report these OOM issues in such detail across multiple threads. It’s clear this is impacting your ability to use Cursor and that’s understandably frustrating.
From what I can see, you’ve been consistently hitting OOM crashes over multiple recent versions on Windows, despite having plenty of RAM available, and you’ve already shared your version info and screenshots. That’s exactly the kind of impact we take seriously, and the team has been trying to follow up with specific questions so they can narrow down where the problem is coming from and how to reproduce it reliably.
Right now, what’s actually slowing us down in helping you is not that the issue isn’t real, but that many of your latest posts repeat the same screenshot and concern across several topics without answering those follow‑up questions or adding new technical context. Cross‑posting, creating new topics for the same underlying problem, and re‑posting the same image into other users’ threads all make it harder for the team to track your case, because it splits the discussion and increases the time spent de‑duplicating instead of debugging.
To give you the best chance of a fix (or at least a solid workaround), could you help us by: removing duplicate parts, replying in one primary OOM thread with the specific info the team requested there already, avoiding new topics about the same crash, and only adding new screenshots or logs when they contain new information or behavior. That way, we have a single, coherent history of your issue that engineering can use to test hypotheses and correlate with changes in Electron, memory limits, and Cursor versions.
We’d really like you to stay engaged as a constructive partner in getting this resolved, because your long‑running reports are valuable if we can line them up with the right details. Please also have a quick read through our community guidelines and keep the discussion focused and actionable so we can prioritize your case effectively: Guidelines - Cursor - Community Forum.
For reference, here are some of your existing threads where we’d suggest consolidating follow‑ups instead of starting new ones:
- OOM problems persist in Cursor 2.3 despite available memory
- Constant OOM code 536870904 with latest update - #15
- Cursor 2.2.36 leaks like a sieve - #55 by Work_Dre
- Cursor is not usable after the last update - #17 by Work_Dre
- Cursor not using available computer memory and causing early out of memory errors when in fact there is plenty of memory - #10 by Work_Dre