Please try attaching another Visual Studio instance to the frozen one and obtaining the call stack as shown on this page. Please attach the call stack here and we will investigate it further.
Thanks, we have reproduced the problem on our side. Turns out, the latest Visual Studio 2019 freezes when trying to select a test without a source location (this only affects the simulation platform, as VisualGDB does not support parsing of the DWARF symbols in Win32 EXEs).
We have updated VisualGDB to report a dummy location for these tests. Please try this build: VisualGDB-5.6.5.4323.msi