ryanborMSFT
commented
1 year ago ms-vscode.azure-account-unresponsive.cpuprofile.txt
Occurred again today when doing something entirely unrelated to Azure. I was building a devcontainer and vscode was stuck as the Azure Accounts extension was bogged down.
alexweininger
Type: Bug
I own about 11,000+ subscriptions, however I only use a few (single-digits) on any given day in vscode.
At this moment, Azure Accounts times out constantly, leading to freeze-ups, etc.
Not sure if this is a bug, feature request, expected behavior, if I'm doing something wrong, etc. Should filtering on subs happen server-side? Once filtered, should the Accounts extension continue to choke on the amount of data it's processing? I feel like vscode is retrieving ALL subs (a process that can take a very long time) and then filtering afterwards. Is there a way I can confirm this one way or another?
Interested to hear if anyone has ideas for a short-term solution, and if the devs have a medium-term feature update to address this, or if I'm just nuts and missing something simple :)
Extension version: 0.11.3 VS Code version: Code 1.76.0 (92da9481c0904c6adfe372c12da3b7748d74bdcb, 2023-03-01T10:22:44.506Z) OS version: Windows_NT x64 10.0.19044 Modes: Sandboxed: No
System Info
|Item|Value| |---|---| |CPUs|AMD Ryzen 9 5900X 12-Core Processor (24 x 3700)| |GPU Status|2d_canvas: enabledcanvas_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)|63.92GB (45.84GB free)| |Process Argv|--crash-reporter-id 4d96d6d8-6eda-4b83-bf3a-34ef5ff8ef37| |Screen Reader|no| |VM|0%|