0

Under unclear circumstances, our VS Code extension is causing a dramatic perf degradation due to a huge number of ripgrep (rg.exe) instances. So far I haven't been able to repro this issue, but based on user reports I believe it was introduced by this change. Can anyone provide some insight into what leads to the execution of rg.exe?

https://github.com/microsoft/vscode/issues/164665

https://github.com/microsoft/sarif-vscode-extension/issues/472

https://github.com/microsoft/sarif-vscode-extension/issues/472#issuecomment-1414396307 <- trace logs linked here

*** EDIT I've seen the two issues cited by 'user' but they did not shed any light on the cause of this behavior.

Easy Rhino
  • 63
  • 1
  • 6
  • Looks like a similar question to [VScode rg process taking all the CPU](/q/75311062). Also [Many rg commands started by vscode that consume 99% of CPUs](/q/65120743) – starball Feb 03 '23 at 21:06
  • 1
    *looks at GitHub link. You... work for microsoft and are using Stack Overflow to source answers for a problem with a Microsoft product? – starball Feb 03 '23 at 21:09
  • 2
    Yes, which makes questions and answers available to everyone. – Easy Rhino Feb 04 '23 at 22:53
  • Isn't rg.exe (in VS Code case, https://github.com/microsoft/vscode-ripgrep) supposed to be used to _monitor/walk_ into every workspace folder you have? If that PR increased somehow the number of folders you are now monitoring, that may be the reason. I think you should compare this, before and after your change. – alefragnani Feb 05 '23 at 13:33
  • Does this answer your question? [Many rg commands started by vscode that consume 99% of CPUs](https://stackoverflow.com/questions/65120743/many-rg-commands-started-by-vscode-that-consume-99-of-cpus) – starball Mar 29 '23 at 03:18

0 Answers0