What is the maximum RAM you were able to allocate for Cursor?
2 Likes
How is this possible? I do not exceed 2GB in large projects
1 Like
Mine sometime 2.3GB when opening Monorepo project.
1 Like
Wow, thats a lot of RAM. How much file you open? its that monorepo? if you believe this is bug, you can also report on Bug Reports - Cursor - Community Forum so they wil give attension for helping solve this problem
Mine never spikes that high, I’m on Mac though. My work computer is 16GB memory and my personal is only 8GB, but I have never had performance issues on either with Cursor.
2 Likes
Agree, its also depends on codebase that you’re open. here example if opening Monorepo Backend, Frontend and Mobile. its almost 4GB. But if open simple repo/project. only cost 2GB.
this was of course super atypical case - IMHO a loop inside the data re migration process and the Cursor started to glitching like this. Had to kill the process , lost the database and after that nicely reverted all to a version from a few hours before
1 Like
My MacBook was frozen. I had to hold down the power button to restart it.
I’ve noticed this problem occurs if I have two workspaces open on two different Cursor windows, and both workspaces contain the same repository (in other words, one repository is open in two windows).
Why you need open 2 workspace that contain same repository?
66 GB? Wow, thats a lot!