Hight CPU usage with the extension enabled.

[cmaiquel]

Type: Bug

The CPU usage of the "Code Helper" process keeps over 50%. This started to happen after the latest version of Code.

Extension version: 3.3.0 VS Code version: Code 1.71.0 (784b0177c56c607789f9638da7b6bf3230d47a8c, 2022-09-01T07:25:38.437Z) OS version: Darwin x64 21.6.0 Modes: Sandboxed: No

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz (8 x 2800)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled metal: disabled_off 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)	8, 7, 5
Memory (System)	16.00GB (2.77GB free)
Process Argv	--crash-reporter-id 314e15c5-f103-43d2-93ad-8e9d6ad48f0d
Screen Reader	no
VM	0%

A/B Experiments

vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30557514
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
pylanb8912:30545647
vsclangdc:30486549
c4g48928:30535728
hb751961:30553087
dsvsc012:30540252
azure-dev_surveyone:30548225
i497e931:30553904

[nealoke]

I have the same issue, basically this plugin makes VS code unusable. Disabling it solved all my issues :(

[steveoh]

Yep, this package creates horrible performance issues. Also disabled. Is there a way to make this nicer on vscode?

[connor4312]

Some suggestions:

• Use esbuild instead of webpack to build the bundles. Downside is this does involve a native bundler, which is hard to ship in a VS Code extension... but you could always install it dynamically in the extension, since people using this extension will have npm installed.
• If you don't use esbuild, move import cost calculation into a subprocess. The extension host is shared between all extensions, and this extension easily blocks it for periods of time.