Breakpoint hit -> window gets focused -> VS Code freezes for some time

[ghost]

• VS Code Version: 1.56.0
• OS Version: Windows_NT x64 10.0.18363

Steps to Reproduce:

1. Set breakpoint in js.-file
2. Launch debug-session in browser (all breakpoints in dev-mode disabled)
3. Switch to browser window
4. Maximize browser (because it is just half open)
5. Hit breakpoint
6. VSCode blinks in taskbar -> switch back to it
7. VSCode freezes and waits for something

Hints:

• By avoiding step 4, this issue doesn't occur.
• Minimizing and maximizing VSCode while its freezed solves this issue.
• This issue also happens in insider-version of VSCode.

Does this issue occur when all extensions are disabled?: Yes

Launch configuration (no, this problem is not related to brave, it happens also in google chrome):

{
    "name": "Browser debug",
    "request": "launch",
    "type": "pwa-chrome",
    "runtimeExecutable": "C:/Program Files/BraveSoftware/Brave-Browser/Application/brave.exe",
    "runtimeArgs": ["--remote-debugging-port=9222"],
    "url": "http://127.0.0.1:5000",
    "webRoot": "${workspaceFolder}\\memory-viewer\\server",
    "pathMapping": {
        "/css": "${workspaceFolder}\\memory-viewer\\server\\static\\css",
        "/app": "${workspaceFolder}\\memory-viewer\\server\\static\\app",
        "/js": "${workspaceFolder}\\memory-viewer\\server\\static\\js"
    }       
},

[avenmore]

This looks like a regression of the issue mentioned in #116865, #117780, and others and declared a duplicate of #114459. It was fixed in 1.55 but it's back. Super annoying.

[ghost]

vscode-debugadapter-b6c8efc1.json.gz

First breakpoint successful, then I triggered it again with no success.

[isidorn]

@MaxHausmann can you reproduce if you start vscode with
code --disable-features=CalculateNativeWinOcclusion <path to workspace/folder>

[ghost]

With
code --disable-features=CalculateNativeWinOcclusion <path to workspace/folder> this issue does not occur.
I tested it with several sizes of the browser-window (see initial text) and the breakpoint got hit instantly.

Additonal information: CMD says "Warning: 'disable-features' is not in the list of known options, but still passed to Electron/Chromium."

[isidorn]

@MaxHausmann lovely thanks a lot.
This happens only on Windows, thus assigning windows flag, and it seems to be electron related thus assigning to my friend @deepak1556

We will investigate if we can fix this as part of the recovery release. If not we plan to fix it in the future

[isidorn]

@MaxHausmann probably not related, but just to be 100% sure if you put

"debug.openDebug": "neverOpen"

In your settings, can you reproduce?

WORKAROUND
Put in your settings

"debug.focusWindowOnBreak": false

[ghost]

With

"debug.openDebug": "neverOpen"

I can reproduce the issue.

With

"debug.focusWindowOnBreak": false

(as the command says) VSCode window does not focus, but breakpoint got hit successfully.

[isidorn]

@MaxHausmann thanks, but if the windows does not get focus there is no freeze?
As for the openDebug setting that is something which we changed this milestone and I just wanted to verify it is not related to this issue.

[ghost]

Yes, there is no freeze. The icon in the taskbar is also not blinking.

[enunez]

This issue has been open for over a year now. Has there been any progress on fixing this bug? Is there an ETA? Has the root cause for the CalculateNativeWinOcclusion bug even been identified yet? I'd prefer not to add a launch flag, because I'm likely to forget to remove it once it eventually gets fixed.

This issue still happens for me on Windows 11 with all the latest updates. It also happens when I simply leave the computer unattended for a while. VSCode hangs and takes ~30s to respond to input again. Same thing happens with certain pages opened in Chrome.

[skaldesh]

I am coming from issue 146737.
If this is the same root cause, then it is not restricted to Windows.

I am on Arch Linux with Sway WM:

Version: 1.67.2
Commit: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
Date: 2022-05-20T07:44:59.452Z
Electron: 17.4.3
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Linux x64 5.15.43-1-lts

I can confirm the bug there as well, that after switching focus from another application back to VSCode, it takes between 1-3s until VSCode becomes responsive again. I am happy to help debug, if need be.

[lorand-horvath]

Solution here: #146737 (comment)

[hannah23280]

This issue still occur for v1.68.1

[lorand-horvath]

This issue still occur for v1.68.1

@hanct Have you tried uninstalling completely and doing a clean install as I described here? #146737 (comment)
The problem is the cache growing to several thousands of files from the initial few hundred. So VSCode slows down to a crawl trying to process all of that.

[skaldesh]

@lorand-horvath
This is no real solution, but a temporary fix.
VSCode must be fixed for the real solution

[lorand-horvath]

@skaldesh Well, it's the ONLY solution that I could find after many months of searching and trying everything possible and impossible.
The interesting thing is that when I mentioned this solution/workaround/temporary fix (call it as you wish), the thread was promptly locked up: #146737 (comment)
Seems like someone is trying to sweep the issue under the proverbial rug...

[hannah23280]

This issue still occur for v1.68.1

@hanct Have you tried uninstalling completely and doing a clean install as I described here? #146737 (comment)
The problem is the cache growing to several thousands of files from the initial few hundred. So VSCode slows down to a crawl trying to process all of that.

I try to avoid that..cos when I start moving the code window (as suggested by others), the breakpoint appear. So I believe nothing to do with the cache sizes.

[hannah23280]

Then I also realize that sometime I don't even need to move the window, the break point response fast..but that is intermittent

[hannah23280]

For now, I try not to do anything so that when there is a fix, I have a broken vscode to prove this fix is working.

[Cr4zyEight]

There is a workaround on disabling this option in VS Code Settings.
By doing this u have to live with the fact that the VS Code icon will not blink in the taskbar when the debugger hits a breakpoint
But the Window will also not freeze

[skaldesh]

I have opened a performance issue via code and attached a performance profile as well, since I got hit by this bug multiple times today. I am on Linux.

#154509