-
Notifications
You must be signed in to change notification settings - Fork 29.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RipGrep using a lot of CPU #40480
Comments
Add to your config |
Which extensions do you have installed? (Help > Report issue to get a list) |
@genuss Does search still work without RipGrep? What is the downside of disabling it? @roblourens See below v
(1 theme extensions excluded) |
Yes but it will be much slower. I'm guessing the first
|
Thanks for the guidance @roblourens! The issue was caused by my forked version of Babel, which contains circular To solve this, I disabled Ripgrep ( So the question now: Why do circular imports (or at least this flavor of them) cause an infinite loop? Googling for the error message, I found #35659, which links to the underlying RipGrep issue BurntSushi/ripgrep#633. Closing this issue as a duplicate. $ "/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/vscode-ripgrep/bin/rg" --files --hidden --case-sensitive -g "*.r|.rd|rmd" --no-ignore --follow --quiet -- .
File system loop found: ./node_modules/babel/packages/babel-standalone/node_modules/@babel/plugin-syntax-object-rest-spread/node_modules/@babel/core/node_modules/@babel/helper-transform-fixture-test-runner/node_modules/@babel/core points to an ancestor ./node_modules/babel/packages/babel-standalone/node_modules/@babel/plugin-syntax-object-rest-spread/node_modules/@babel/core
File system loop found: ./node_modules/babel/packages/babel-standalone/node_modules/@babel/plugin-syntax-object-rest-spread/node_modules/@babel/core/node_modules/@babel/register/node_modules/@babel/core points to an ancestor ./node_modules/babel/packages/babel-standalone/node_modules/@babel/plugin-syntax-object-rest-spread/node_modules/@babel/core
... |
Thanks for investigating that. Ripgrep probably isn't getting into an infinite loop, but is slow in following lots of symlinks. One thing you can try - reenable ripgrep and tell it not to follow symlinks, with |
@roblourens You're right it's possible that it's just slow - I've been running that
|
OSX's Activity Monitor reports two
rg
processes pegged around 350% CPU. My machine is really slow, and fans are spinning loudly.Steps to Reproduce:
Reproduces without extensions: No
The text was updated successfully, but these errors were encountered: