many rg.exe spawn in background 100% CPU usage

[ZanzyTHEbar]

Type: Bug

1. Have extension turned on
2. Use a compiled language, like Typescript, rust or C++
3. import/include/use a library/modual or try to compile

Watch the CPU usage spike, hudreds of rg.exe spawn as tasks.

The issues does not resolve until vscode is closed or the extension disabled - even when compilation is finished - issue persists.

Extension version: 3.15.6 VS Code version: Code 1.73.0 (8fa188b2b301d36553cbc9ce1b0a146ccb93351f, 2022-11-01T15:34:06.111Z) OS version: Windows_NT x64 10.0.19045 Modes: Sandboxed: No

System Info

|Item|Value| |---|---| |CPUs|AMD Ryzen 7 3700X 8-Core Processor (16 x 3593)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|undefined| |Memory (System)|31.95GB (16.72GB free)| |Process Argv|-n --crash-reporter-id 8dc70ebe-c15f-4ba8-a6d3-cf4ca0661432| |Screen Reader|no| |VM|0%|

A/B Experiments

``` vsliv368:30146709 vsreu685:30147344 python383cf:30185419 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492:30256859 vstes627:30244334 vslsvsres303:30308271 pythonvspyl392:30443607 vserr242cf:30382550 pythontb:30283811 vsjup518:30340749 pythonptprofiler:30281270 vshan820:30294714 vstes263cf:30335440 vscoreces:30445986 pythondataviewer:30285071 vscod805cf:30301675 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 cmake_vspar411:30581797 vsaa593cf:30376535 pythonvs932:30410667 cppdebug:30492333 vsclangdf:30486550 c4g48928:30535728 dsvsc012:30540252 azure-dev_surveyone:30548225 pyindex848cf:30577861 nodejswelcome1cf:30587006 fc301958:30595537 3biah626:30602489 gswce1:30605430 3d0df643:30604793 dbltrim-noruby:30604474 ```

[ZanzyTHEbar]

found out there extensive testing - it was actually rust-analyzer that was causing the issue. Extension Bisect just failed to find it - disabling One Dark Pro seemed to solve the problem - but a few hours later it came back with a vengenace. Turns out - it wasn't this extension.