Check the Forum
I’ve looked through the forum briefly but couldn’t find a post that exactly matches this issue. If this has already been reporte
d, please let me know, and I’ll add my details there instead.
Description of the Bug
I’m extremely frustrated with Cursor right now. I’m running version 0.47.8, and the application keeps crashing with an “out of memory” (oom) error, showing the code -536870904. On top of that, before it crashes, I often get a “The window is not responding” message, which freezes the app and forces me to either wait, reopen, or close it. This is completely disrupting my workflow! I’m losing unsaved work, and it’s making Cursor almost unusable for me, especially when I’m working on larger projects. I rely on this tool for my coding, and these constant crashes are driving me up the wall.
Steps to Reproduce the Bug
I’m not 100% sure of the exact steps to reproduce this, but here’s what I’ve noticed:
-
I’m working on a fairly large project with multiple files open in Cursor (version 0.47.8).
-
I’m using WSL2 (Windows Subsystem for Linux 2) with 16GB of RAM allocated to it, while my PC has 32GB of RAM total.
-
I’m doing normal tasks like editing code, debugging, or letting Cursor index my project.
-
After some time (especially if I have other apps open), the window either freezes with a “The window is not responding” message or crashes entirely with the “oom” error.
It seems to happen more often when I’m working on bigger codebases or if I’ve had Cursor open for a while. I suspect it might be a memory leak or something related to WSL2’s memory allocation, but I’m not a developer of this app—I just want it to work!
Screenshots
I’ve attached screenshots to show the issue:
-
The crash dialog: “The window terminated unexpectedly (reason: ‘oom’, code: ‘-536870904’)”.
-
The “window not responding” message I get before the crash.
-
The “About” dialog with my Cursor version and system details.
System Details
-
Operating System: Windows NT x64 10.0.26100
-
WSL2 Setup: I’m using WSL2 with 4GB of RAM allocated to it.
-
PC Specs: My PC has 32GB of RAM total.
-
Cursor Version: 0.47.8 (user setup)
-
VSCode Version: 1.96.2
-
Commit: 82ef0f61c01d07d91b7e5ab0d488499d5af500e
-
Date: 2025-03-18T05:39:50.993Z (6 days ago as of March 24, 2025)
-
Electron: 32.2.6
-
Chromium: 128.0.6613.186
-
Node.js: 20.18.1
Impact on Using Cursor
Yes, this issue is making Cursor nearly unusable for me. The crashes are bad enough, but the “window not responding” freezes are just as frustrating because I have to stop everything and either wait or restart the app. I’m losing unsaved changes, and it’s slowing down my work significantly. I really need a fix for this ASAP—I can’t keep dealing with this while trying to get my coding done.
Additional Comments
I’ve tried closing other apps to free up memory, but this shouldn’t be happening in the first place, especially since my PC has 32GB of RAM. Could this be related to WSL2’s memory allocation? I’ve set WSL2 to use 4GB of RAM—maybe that’s not enough for Cursor? Is there a memory leak in this version? Can the team please look into this urgently? I love Cursor when it works, but right now, it’s causing me more stress than it’s worth. I’d really appreciate any help or updates on a fix. Thanks!
This updated post now includes the WSL2 and RAM details, which might help the Cursor team identify if the issue is related to WSL2’s memory constraints or how Cursor interacts with WSL2. You can copy this text, paste it into the Cursor forum, and attach the screenshots. Let me know if you’d like further adjustments!