vscode: When using Profiles, a lot of Extensions is not loaded

Type: Bug

I have utilized the Profiles feature. So I have a lot of different profiles. as a example some profiles are using Java and some are not. So with Spring Boot.

Very often, when I open a project it seems like extension, disabled by some (other?) profiles, are lost when project are loaded.

Typical message is :

Cannot activate the ‘Spring Boot Dashboard’ extension because it depends on the ‘Spring Boot Tools’ extension, which is not installed. Would you like to install the extension and reload the window?

I also get sometimes a message that the extensions could not be installed because of the extentions folder is not there or is in use

VS Code version: Code 1.77.3 (704ed70d4fd1c6bd6342c436f1ede30d1cff4710, 2023-04-12T09:16:02.548Z) OS version: Windows_NT x64 10.0.19045 Modes: Sandboxed: Yes

System Info
Item Value
CPUs 11th Gen Intel® Core™ i9-11950H @ 2.60GHz (16 x 2611)
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) 63.71GB (38.35GB free)
Process Argv –crash-reporter-id 20917981-573b-440b-b671-e861aa1e63be
Screen Reader no
VM 0%
Extensions (25)
Extension Author (truncated) Version
terminal-commands adr 1.0.5
terminal-loader ari 1.2.1
gitlens eam 13.5.0
rest-client hum 0.25.1
git-graph mhu 1.30.0
jupyter-keymap ms- 1.1.0
remote-ssh ms- 0.100.0
remote-ssh-edit ms- 0.84.0
remote-wsl ms- 0.77.0
vscode-remote-extensionpack ms- 0.24.0
remote-explorer ms- 0.4.0
remote-server ms- 1.0.0
fabric8-analytics red 0.3.6
java red 1.17.0
vscode-yaml red 1.12.2
vscode-boot-dev-pack vmw 0.2.1
vscode-java-debug vsc 0.49.1
vscode-java-dependency vsc 0.21.2
vscode-java-pack vsc 0.25.10
vscode-java-test vsc 0.38.2
vscode-lombok vsc 1.1.0
vscode-maven vsc 0.41.0
vscode-spring-boot-dashboard vsc 0.12.0
vscode-spring-initializr vsc 0.11.2
terminal-all-in-one yas 1.12.0
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30610678
nodejswelcome1:30587005
2e4cg342:30602488
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
a9j8j154:30646983
vsctsb:30705553
azdwalk:30721579
pythonms35:30701012
pythonfmttextcf:30716743
pythonclientmvcf:30713944

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 20 (6 by maintainers)

Most upvoted comments

So far not seeing the reported issue with Insiders. Vacation up next, så further reporting is after summer