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:
Tee,
Thank you for your reply. It gives me hope that there might be some relief from the frustration of dealing with this repeating problem. Regular communication with users is important for a healthy relationship, and I encourage you and the staff to keep responding to the latest entries about an issue.
I am worried that you are not aware of the entries I’ve made on these posts. I have tried all workarounds and provided all the information asked of me. The problem still exists. That said, I might have missed a post; if so, I would appreciate your follow-up after reading my responses. My goal in posting the screenshots was to show proof that the OOM issue is widespread and seriously disruptive, not to overload the system.
One reason for my multiple posts is my evolving understanding of the issues. At first, I thought it was a specific problem with version 2.2.36, and I included that version in the ticket title. I then found that the problem occurred in other versions of the IDE. I looked for a way to edit the title but couldn’t find one, so I created a new post with “2.x.x” in the title to show it wasn’t limited to 2.2.36. I then read another post saying that Cursor was significantly limited because it exists in a wrapper (Electron). This widened my view, and I submitted another ticket asking for a newer version of the wrapper that supports 8GB.
Knowing what I know now, I would have made the ticket titles more general so there would be no need to create new ones.
I am fine combining tickets, but I can’t find instructions on how to do that. Please tell me which one to use, and I’ll stick with that.
For now, let me know what I need to try that I haven’t already posted, and I’ll work on it immediately.
Thanks again for your attention to this issue. I know we all want the OOM problems fixed once and for all for the good of the entire Cursor user community.
Really appreciate your feedback and willingness to help with the issue.
Check following thread if you have tried this and respond there, seems other users have found workarounds, try also setting that memory limit higher to allow more time between crashes. When you see memory increase, go to Help > Open Process Explorer, sort by mem and take a screenshot, paste it in mentioned thread. Use following thread as this has the latest version of Cursor. You can share also your version details there.
I have removed the duplicate screenshots across many threads and kept all that have specific info. This issue affects some users but we really need more info on what causes the increase in memory usage, as just setting higher memory limits for everyone would cause other issues.
As this thread went into more of a conversation between you and me I will unlist it.
