VSCode stopped working after upgrade from 1.78.2 to 1.79

[ghost]

Type: Bug

Hello - I'm not sure what the issue is but VSCode helped me narrow it down to this extension. The bug caused no extensions to be recognized (in settings.json for instance) - the extensions were still listed but almost all context menu items were disabled for them and the listings were all greyed out... The symptom that alerted me to the problem initially was that I could not open the Release Notes or Welcome page immediately after I upgraded visual-studio-code-bin (1.78.2-1 -> 1.79.0-1) on Manjaro (Arch) Linux.

Extension version: 0.6.0 VS Code version: Code 1.79.0 (b380da4ef1ee00e224a15c1d4d9793e27c2b6302, 2023-06-07T14:28:44.251Z) OS version: Linux x64 5.15.114-2-MANJARO

Here's what I found in the log:

```log 2023-06-08 19:08:58.989 [error] Cannot read properties of undefined (reading '_lower'): TypeError: Cannot read properties of undefined (reading '_lower') at C.toKey (vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:656:8213) at S.get (vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:656:8608) at e.ExtensionRunningLocationTracker.l (vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:2607:11783) at e.ExtensionRunningLocationTracker.initializeRunningLocation (vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:2607:12441) at e.NativeExtensionService.ib (vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:2607:19698) at e.NativeExtensionService.hb (vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:2607:19280) 2023-06-08 19:08:59.098 [error] Cannot read properties of undefined (reading '_lower'): TypeError: Cannot read properties of undefined (reading '_lower') at C.toKey (vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:656:8213) at S.get (vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:656:8608) at e.ExtensionRunningLocationTracker.l (vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:2607:11783) at e.ExtensionRunningLocationTracker.computeRunningLocation (vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:2607:11331) at Object.getInitData (vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:2608:15857) at async e.NativeLocalProcessExtensionHost.J (vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:1635:8698) ```

System Info

|Item|Value| |---|---| |CPUs|AMD Ryzen 5 5600X 6-Core Processor (12 x 3700)| |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
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|1, 1, 0| |Memory (System)|31.26GB (28.41GB free)| |Process Argv|| |Screen Reader|no| |VM|0%| |DESKTOP_SESSION|xfce| |XDG_CURRENT_DESKTOP|XFCE| |XDG_SESSION_DESKTOP|xfce| |XDG_SESSION_TYPE|x11|

[ArturoDent]

Thanks for the report. How did VSCode help you to figure out this extension was an issue? There isn't anything in the log related to the extension.

I had issues with the v1.79 update too and have Command Alias installed as well. But eventually the problem went away with some restarts, etc. (I am not sure how it got fixed) but I never uninstalled any extensions and the Extension Bisect was unhelpful.

[ghost]

I used the Extension Bisect. After it disabled this extension and restarted, everything was working again.

[talanb]

I had the same issue after upgrading to v1.79 and also was able to resolve the problem after Extension Bisect identified this extension as the culprit