Cursor crashes with OOM error everytime after opening my only relevant workspace.
The workspace combines two repos from separate folders.
I have Windows 11 and the repos are used via WSL
I have tried everything, removing, renaming, reinstalling, using older version of Cursor.
Nothing helps. I have been an Ultra user for a year, but will have to ditch Cursor very soon.
Hey, thanks for the report. We’ve had a few reports of similar crashes in recent versions, and the team is aware and tracking it.
That said, your case is a bit specific since it happens within 30 seconds in a multi-root WSL workspace. Let’s narrow it down:
Open each repo separately instead of using a multi-root workspace. Does it still crash? This will tell us if having two WSL repos in one workspace is the trigger.
Try without extensions:
cursor --disable-extensions
Disable GPU acceleration:
cursor --disable-gpu
Reset Cursor state (your settings will be backed up):
# In PowerShell
Rename-Item "$env:APPDATA\Cursor" "CursorBackup"
Open Process Explorer right after launch (before it crashes): Ctrl+Shift+P > Developer: Open Process Explorer and take a screenshot showing which process is using memory.
Also, can you share:
Your installed extensions list
The main.log from Help > Open Logs Folder (around the time of the crash)
The approximate size of both repos (file and folder count)
Whether you’re using any MCP servers
Let me know what you find, especially if opening the repos in two separate windows makes a difference.
Hi Dean,
Thanks for the reply.
I used a couple of days last week battling this so I wont try everything now, but here is some context and answers to some of your questions:
I was mistaken, with the old version 2.5.26 the bug does not happen, I thought it happens in the old version too, but that was because I did not realize there was an auto update in the background.
So only the latest 2.6.11 version is the problem, though obviously I dont want to use old versions in the future.
No, Cursor does not crash if I open folders separately, only if I open the workspace file that includes both repos, or even if I try to combine the two repos in a new folder with symlinks to the folders and then try to open and use that new folder.
I will try those other things when I have time and give more info.
Hope that you get this resolved, really like Cursor, was just frustrated last week after using a couple of days on this error.
I am optimistic since the old version still works fine and does not crash.
