Description
System: Red Hat Enterprise Linux Workstation release 7.9 (Maipo)
OS: Linux myhost 3.10.0-1160.36.2.el7.x86_64 #1 SMP Thu Jul 8 02:53:40 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
This began as an occasional annoyance and has escalated into a 100% reproducible annoyance.
Using the latest snap install, during normal editing/debugging/etc. on local system. With increasing frequency, Ctrl-O/File->Open would completely freeze the UI with just a blinking cursor. Sometimes switching away and back would repaint part of the screen, increasingly not. Tried switching the output window to various things before attempting the file open (extension manager, main window, etc), but no output was observed before the freeze.
Once the UI is frozen, only kill/killall seems to be able to get rid of it. Not sure if it means anything, but de-maximize and maximize still resize the window frame, although the contents aren't redrawn. Can't remember if that requires app cooperation or it that is a pure WM thing.
Using snap installed code-insiders made no difference.
Uninstalling snap versions and downloading 1.65.0 from the MS repo so far seems to have restored functionality (1.66.0 requires a glibc version unavailable for RHEL7).
Haven't tried with (all) extensions disabled, but did disable everything I don't need constantly.
One change in workflow recently seems suspiciously coordinated with the start of the issues - began using VS Code on another machine (nfs-mounted home folder, so shared settings/etc.) to attach to running containers (as container-specific user, to specific folder inside container), debug processes inside container, etc.
Perhaps something got saved in the settings that is redirecting local File->Open to the remote-containers extension? Probably not, but the timing is mighty suspicious.