You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a build of my project on Linux, this extension (and each of the extensions it's forked from) starts hundreds of ripgrep processes.
If I simply disable this extension I see no hammering of the CPU.
Here is an example of one of the processes (they all have the exact same parameters) of which I believe it probably starts one process per file created during build.
When running a build of my project on Linux, this extension (and each of the extensions it's forked from) starts hundreds of
ripgrep
processes.If I simply disable this extension I see no hammering of the CPU.
Here is an example of one of the processes (they all have the exact same parameters) of which I believe it probably starts one process per file created during build.
The extension is literally unusable on Linux with this flaw. For reference this issue isn't present when running the build under Windows.
The text was updated successfully, but these errors were encountered: