Bug: Variables in debugger only show up after minimizing and maximizing VS Code

[nickzhums]

trafficstars

https://user-images.githubusercontent.com/56864335/142805699-65672c09-491d-4c22-8d4c-c19b35e610cc.mp4

When interviewing a customer, he mentioned an issue where he starts an app and hit the breakpoint, the variables won't be displayed, but when he minimized and maximized again, the variables show up

the video reproduces this issue and he constantly encounters it

Creating issue here to track and triage

[testforstephen]

Cannot reproduce it with spring-petclinic on my machine, and switch between browser and vscode, the breakpoint is hit immediately.

Hard to tell what's the problem from the short screencast, could you ask him to provide a minimal sample to help us reproduce it?

[nickzhums]

sure, will ask

[Tospaa]

Hello everyone,

First of all, thanks for your attention. I see this issue is opened under vscode-java-pack repo but it's actually a VS Code issue in general. I've a proof in my screencast here:

Video link (I couldn't attach here because it was too big): https://drive.google.com/file/d/1xIoENYCvdDDDBto_Lufmpco_eJH_9sld/view?usp=sharing

Here's the application I've used while reproducing the issue along with some information about my computer like VS Code, Java and Maven binary versions, my VS Code extensions list and my VS Code user settings: https://drive.google.com/file/d/1d7j93D_5k7_SibcBdDMdOD2qOxOqu6F8/view?usp=sharing

Thanks again!

[testforstephen]

@Tospaa Thanks for the additional information. macOS works fine, but I was able to reproduce it on Windows.

I maximized my VS Code window, then switched to the browser and maximized it. When refreshing the browser page to trigger a breakpoint in my Java program, the VS Code icon on the status bar is blinking. However, when clicking on it to display the VS Code window, the breakpoint location is not highlighted and the VS Code window seems to be frozen. minimizing and maximizing VS Code can restore the debugger state.

We'll report this issue back to the upstream VS Code repo.

[testforstephen]

The upstream issue is https://github.com/microsoft/vscode/issues/137772