Cursor is now unusable for me in large repos with many symlinks. Since 2.5 up to 2.6.11 opening Cursor with the repo opened leads to two “rg” processes with very high CPU usage. These processes remain or if they terminate, up to six new “rg” processes appear, leading to extreme CPU usage and Cursor being unusable.
In previous versions, rg would sometimes open at launch but finish in a minute or two. Setting follow symlinks to false as well as “ignore symlinks in cursor ignore search” and adding some folders to .cursorignore completely solved this in Cursor 2.4.37. I have tested this multiple times – 2.4.37 remains problem-free, but anything past 2.5 leads to this issue, despite all the settings plus .cursoginore set up. The rg processes actually access folder that are specifically in .cursorignore – so it seems like it is being skipped.
Steps to Reproduce
Open Cursor 2.5+ in a large repo with extensive symlinks and monitor rg processes.
Expected Behavior
As on 2.4 – opening a repo with symlinks, with all relevant options being turned on or off and .cursorignore set up properly should not spawn persistent, high CPU using processes that make Cursor unusable
I mentioned having the first setting off in my original comment. It did fix this behavior in 2.4, but not in 2.5 nor 2.6.
I have tried the turning off the third-party import as you suggested, on the latest 2.6. Unfortunately, nothing changed, even after restarting Cursor upon the setting change.
There must’ve been some sort of a change between 2.4 and 2.5. On 2.4 the behavior seems clearly linked to the symlinks during discovery, but on 2.5+, rg seems to run in circles regardless, as long as the repo si large with symlinks throughout. I tried opening a small and simple repo and this is not an issue at all there, even on the latest version.
any updates here? I am still stuck on version 2.4. I tried 2.6 with the latest update but the behavior continues. I checked the “rg” process and it’s constantly looking at folders which are specifically added to .cursorignore, so there seems to be some issue with this as well.
