node_modules\@vscode\ripgrep\bin\rg is taking a lot of resources

[hazho]

node_modules@vscode\ripgrep\bin\rg on WSL is consuming lots of resources especially CPU and especially when the "Microsoft edge extension" is installed

this is similar to #186279

• VS Code Version: February 2025 (version 1.98)
• OS Version: WSL Ubuntu 22.04LTS

Steps to Reproduce:

1. install "Microsoft edge extension" and leave it enabled
2. do any action, for example a search or anything else in the explorer

[vs-code-engineering]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.98.2. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[albertosantini]

See also #233703

[roblourens]

https://github.com/microsoft/vscode/wiki/Search-Issues

[GongT]

I've faced this issue on my Windows+Linux SSH setup: enabling "GitHub.copilot-chat" immediately spawns 2–5 rg processes on the remote, maxing out CPU. They respawn shortly after being killed.

/root/.vscode-server-insiders/cli/servers/Insiders-145c1854e758de327fc307453ee05e3d46edd9b9/server/node_modules/@vscode/ripgrep/bin/rg
--files
--hidden
--case-sensitive
--no-require-git
-g
/.github/agents/*.md
-g
!**/.git
-g
!**/.svn
-g
!**/.hg
-g
!**/.DS_Store
-g
!**/Thumbs.db
-g
!**/__pycache__
-g
!**/.classpath
-g
!**/.factorypath
-g
!**/.project
-g
!**/.settings
-g
!**/*.pyc
--no-ignore
--follow
--no-config
--no-ignore-global

When I run it manually, it outputs this: (I'm using pnpm workspace)

rg: File system loop found: ./xxxx/node_modules/aaaaaaa points to an ancestor ./yyyy/node_modules/bbbbbbb

I figured that since __pycache__ is ignored, node_modules should be too.

[Hao-Wu]

I've faced this issue on my Windows+Linux SSH setup: enabling "GitHub.copilot-chat" immediately spawns 2–5 rg processes on the remote, maxing out CPU. They respawn shortly after being killed.

/root/.vscode-server-insiders/cli/servers/Insiders-145c1854e758de327fc307453ee05e3d46edd9b9/server/node_modules/@vscode/ripgrep/bin/rg
--files
--hidden
--case-sensitive
--no-require-git
-g
/.github/agents/*.md
-g
!**/.git
-g
!**/.svn
-g
!**/.hg
-g
!**/.DS_Store
-g
!**/Thumbs.db
-g
!**/__pycache__
-g
!**/.classpath
-g
!**/.factorypath
-g
!**/.project
-g
!**/.settings
-g
!**/*.pyc
--no-ignore
--follow
--no-config
--no-ignore-global

When I run it manually, it outputs this: (I'm using pnpm workspace)

rg: File system loop found: ./xxxx/node_modules/aaaaaaa points to an ancestor ./yyyy/node_modules/bbbbbbb

I figured that since __pycache__ is ignored, node_modules should be too.

Also reported: #318897

In my case, the VS Code window was opened with a mixed frontend/backend multi-root workspace. One folder was a Java backend project, and another folder was a large frontend project with a big pnpm/node_modules tree. rg was triggered by the Java backend folder, but because the VS Code window was a mixed multi-root workspace, the resulting file discovery also traversed the large frontend project. Instead of being effectively limited to the Java backend, it ended up scanning the frontend dependency tree as well.
As a workaround, I removed the Java backend folder from that mixed workspace and reloaded the VS Code window. The high-CPU rg processes disappeared immediately.