lldb-dap vscode extension sometimes shows the wrong stack frame

When using the lldb-dap vscode extension, sometimes the "Call stack" section of the debug view shows one stack frame as selected, but the debug console treats a different stack frame as active (e.g. as indicated by the `f` command).

For me the most consistent way to reproduce this is to collapse the "Variables" section of the debug view: while it's collapsed, clicking in the call stack view changes the active stack frame in the UI (e.g. it's highlighted, the editor moves to that line of code, etc), but those clicks have no effect on the state seen in the debug console.

More insidiously, it sometimes gets into a state where, after selecting a stack frame, the next command in the debug console is executed in the old frame, but then the state updates, and subsequent commands are correctly executed in the frame I selected. I haven't been able to work out exactly what triggers this behavior, but it seems to happen when repeatedly switching between the same frames. I have a screen recording showing the problem, but I can't seem to attach it here.

At risk of stating the obvious, it is _extremely_ disruptive when your debugger sporadically gives you incorrect information.