Window not focused on breakpoint hit when Chrome and VS Code maximized

[zmechanic]

Issue Type: Bug

Steps:

1. Set breakpoint in JSX code.
2. Breakpoint hit and code execution suspended

Expected:
Yellow highlight on line where breakpoint hit; being able to see current variable values.

Observed:
No higlight, VSCode halted (can't click inside). Need to switch to Chrome and back to VSCode. This will immediately indicate breakpoint line with yellow, and can see variables. Seems like focus issue.

VS Code version: Code 1.53.2 (622cb03, 2021-02-11T11:48:04.245Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (8 x 2494)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on protected_video_decode: unavailable_off rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.91GB (6.53GB free)
Process Argv	--crash-reporter-id 6bc32b6e-4df0-47fc-ad3c-da7600333664
Screen Reader	no
VM	0%

Extensions (3)

Extension	Author (truncated)	Version
vscode-eslint	dba	2.1.14
dotenv	mik	1.0.1
debugger-for-chrome	msj	4.12.12

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspyt653:30253241
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vstry244:30256636
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30251590

[isidorn]

@zmechanic

1. can you please share some minimal project for which you can reproduce this?
2. Can you reproduce with VS Code insiders since we pushed some commit that might fix this https://code.visualstudio.com/insiders/
3. Can you post a screenshot

fyi @connor4312

[zmechanic]

Hi, I found when it happens, and when not. When I put Chrome window and VSCode window side-by-side, it works as expected. Breakpoint line is immediately highlighted in VSCode. I put them side-by-side just to take a screenshot for you, and I found that it worked. However, as I only have one 15" screen on laptop, I run Chrome and VSCode maximized. And this is when it's not happening. VSCode icon starts blinking yellow, but when I expand it, no breakpoint highlight, and VSCode appears to hang, it doesn't react to clicks. I need to flip to some other app, and then back to VSCode so that it becomes responsive and shows breakpoint highlight. I used to be a desktop app developer, and experienced an identical issue with our WPF app. There was something with focus on app activation. I know VSCode is Electron based, but the behaviour seems identical to me. Thanks, Alex

…

On Mon, Feb 15, 2021 at 10:51 AM Isidor Nikolic ***@***.***> wrote: @zmechanic <https://github.com/zmechanic> 1. can you please share some minimal project for which you can reproduce this? 2. Can you reproduce with VS Code insiders since we pushed some commit that might fix this https://code.visualstudio.com/insiders/ 3. Can you post a screenshot fyi @connor4312 <https://github.com/connor4312> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#116615 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADEROOMG55F5YORWRSHXIZTS7D4CFANCNFSM4XSCGFFA> .

[isidorn]

So this sounds like focusing the window does not work if Chrome is open side by side.
Sounds like an Electron issue, also assigning to @deepak1556 since I know we already had users complaining that window.focus sometimes does not work

[zmechanic]

No, it's opposite. Side-by-side works OK. Both maximized doesn't work.

…

On Mon, Feb 15, 2021 at 12:59 PM Isidor Nikolic ***@***.***> wrote: So this sounds like focusing the window does not work if Chrome is open side by side. Sounds like an Electron issue, also assigning to @deepak1556 <https://github.com/deepak1556> since I know we already had users complaining that window.focus sometimes does not work — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#116615 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADEROONUQYBFDNPMS5JTPVTS7ELBRANCNFSM4XSCGFFA> .

[deepak1556]

Can you check if the issue continues to happen when you start the app like code --disable-features=CalculateNativeWinOcclusion

[zmechanic]

You are right. The disable feature fixes the issue.

…

On Mon, Feb 15, 2021 at 10:18 PM Robo ***@***.***> wrote: Can you check if the issue continues to happen when you start the app like code --disable-features=CalculateNativeWinOcclusion — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#116615 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADEROOIZIW4BGCOLADXAYG3S7GMUZANCNFSM4XSCGFFA> .

[deepak1556]

Thanks for checking, merging the issue to #114459. Please follow that issue for updates.