Hey friends,
Over the past 2-3 days, Cursor has been a RAM glutton.
Even though I restart it every morning.
Any ideas why?
Think we have a bug with our memory usage that will be fixed in our next release.
The next release should be a fix for this. If it does not it would also be helpful if you could run the following inside Cursor:
- press
cmd+shift+p, then enterdeveloper: log database storage contents - press
cmd+shift+p, then enterdeveloper: open logs folder - zip that full folder up and send it to hi@cursor.so
I also wanted to report that cursor significantly slows down my macbook pro. I think it may be due to the memmory usage, which forces it to use the swap, but I am not sure. Let’s see what happens after the hotfix
Nope.
My current workflow is still open cursor, do any edits, and then close it because it starts to slow down my computer if it stays open for too long.
If that matters, I also have VSCode open at the same time.
Could you try running the same steps as above:
- press
cmd+shift+p, then enterdeveloper: log database storage contents - press
cmd+shift+p, then enterdeveloper: open logs folder - zip that full folder up and send it to hi@cursor.so
@danielo Just checking in here. How long do you keep the editor open for? Do you have a sense of if this happens for all types of projects or just a few specific ones?
As soon as I open it, it starts to eat memory and increase my resource usage. Because it worked that bad I didn’t tried in any other project, because some times it forces me to reboot my computer, interrupting my workflow quite a bit
If you could, it’d also be incredibly helpful if you could go to developer tools, then “Performance,” and take a profile and send it to us.
Will try to do that
Sorry, the file you are trying to upload is not authorized (authorized extensions: jpg, jpeg, png, gif, heic, heif, webp, avif).
Could you email to michael@cursor.so?