I’m also on 2.4.31 on a MacBook and mine causes “out of memory” crashes in less than an hour.
cursor is working pretty badly after last update, when i click to type text in the context window - everything is just being frozen for me, still have like 18GB RAM free. Cant use the app, please fix @condor
Thank you all for the feedback. It looks like we fixed issues for some and still need to do more for others.
We would need more specific and clear info that helps us reproduce remaining issues:
- Does this occur in latest version? Post the full version string.
- In which cases does it still occur?
- Does it happen when you open a new empty project?
- Only on existing chats or also on new chat?
- What consumes most memory? Help > Open Process Explorer, take screenshot
Here are a few more checks, please try them to help us narrow down the causes of your specific case:
Windows:
Mac:
- For those on M1-M5 Macs, please use the ARM version of Cursor from Cursor · Download for improved performance.
Maybe it is again to early. But as previosly my IDE was crashing every 5m, now it looks stable. On my linux machine previously i removed .cache/cursor which didn’t help. Now i used rm -rf ~/.config/Cursor and remove cursor from .local/**. After that it behaves like clean installation. No freeze so far.
Version: 2.4.31
VSCode Version: 1.105.1
Commit: 3578107fdf149b00059ddad37048220e41681000
Date: 2026-02-08T07:42:24.999Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Linux x64 6.17.0-5-generic
Well after few hours of peaceful coding the crashing is back on menu
Over here it takes ages to start up. Sometimes even minutes.
It’s a multi billion company that offers a paid tool, and you’re gaslighting paying customers by saying we need to live with it because our products don’t always work? Right…
only 41% of RAM is busy,
In which cases does it still occur? - i just open the app and if i have old chat - it gonna be frozen, so i had to archive them. I believe problem are old chats and this saving UI state feature that i never faced before until last update. New project and new agents working fine, thank you.
In which cases does it still occur? - i just open the app and if i have old chat - it gonna be frozen, so i had to archive them. I believe problem are old chats and this saving UI state feature that i never faced before until last update. New project and new agents working fine, thank you.
I’m on Arch Linux and my cursor version is 2.4.35. I got in the habit of keeping chats somewhat small. I have AI generate .md files and do a few of those markdowns as they’re just todo files. Then, after a few of those I just create a new chat. So, my workflow consists of .md files where some serve as context for new chat sessions. Anyways that solves this whole issue and it forces me to create checkpoints which isn’t bad. But I do agree it’s annoying having to come up with a strategy to work with/use cursor. But it’s well worth it imo
hi @Marti the post from Treumuth is sarcasm, they are not part of Cursor team.
Hey all!
This should be fixed as of the latest versions of 2.5. Thanks for the reports.
Definitely seems to be fixed on my end. Thanks so much!