New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 905564 link

Starred by 2 users
Status: Assigned
Owner:
sunn...@chromium.org
Cc:
█ manoranj...@chromium.org
nyerramilli@chromium.org
rbasuvula@chromium.org
zmo@chromium.org
dsinclair@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression:'Report an issue' overlay turns black momentarily while loading

Reported by vineetha...@etouch.net, Nov 15 
Chrome Version: 72.0.3610.2 (Official Build) Revision d1388eea987cd8f0f0e28b3570cded07eebae848-refs/branch-heads/3610@{#8}(32/64-bit)
OS: Windows 10

What steps will reproduce the problem?
1. Launch chrome, click on Wrench Menu(3 dots) > Help > 'Report an issue'.
2. Observe when 'Report an issue' window gets launched.

Actual Result  : 'Report an issue' overlay turns black momentarily while loading.
Expected Result: 'Report an issue' overlay should not turn black while loading.

This is a regression issue broken in ‘M-72’ and below is the 'per-revision' bisect information:
Good Build : 72.0.3605.0 (Revision : 606282)
Bad Build  : 72.0.3606.0 (Revision : 606693)

You are probably looking for a change made after 606311 (known good), but no later than 606312 (first known bad).

CHANGE-LOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+log/7b104eccb81d860641246c2780416186a5267d07..eec86ff6c03b228b426a4553c89724d04e0a0f56

Suspect: https://chromium.googlesource.com/chromium/src/+/eec86ff6c03b228b426a4553c89724d04e0a0f56

@sunnyps: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Kindly refer the attached screen-cast.

Note: Issue is specific to Win-10 OS.

Thank you
ActualVideo.mp4
579 KB View Download
ExpectedVideo.mp4
670 KB View Download

Comment 1 by nyerramilli@chromium.org, Nov 15

Cc: manoranj...@chromium.org
Labels: ReleaseBlock-Stable
marking as RBS, please change if required.

Comment 2 by rbasuvula@chromium.org, Nov 21 

Friendly ping! Could you please provide any update on this issue as it has been marked as a stable blocker.

Thank You!

Comment 3 by vineetha...@etouch.net, Nov 21 

Update:

Rechecked the above issue on Windows 10 OS using latest available Canary build #72.0.3616.0 and the issue is still reproducible.

Thank you
Canary_Behaviour.mp4
575 KB View Download

Comment 4 by rbasuvula@chromium.org, Nov 26 

Gentle ping! Could you please provide any update on this issue as it has been marked as a stable blocker.

Thank You!

Comment 5 by rbasuvula@chromium.org, Dec 3 

Gentle ping! Could you please provide any update on this issue as it has been marked as a stable blocker.

Thank You!

Comment 6 by sunn...@chromium.org, Dec 4

Cc: zmo@chromium.org
Components: Internals>GPU>Internals
Labels: -Pri-1 -ReleaseBlock-Stable Pri-2
Not R-B-S

The above CL only reintroduced the bug because we had direct composition disabled briefly on trunk and the CL only re-enabled it.

I suspect this happens because of the first frame of root surface swap chain being dropped by direct composition similar to what's documented here for video swap chains: https://cs.chromium.org/chromium/src/gpu/ipc/service/direct_composition_surface_win.cc?rcl=68520e01bfff88e3a01129e9f234760efb63ebcb&l=1031

We can test adding the same workaround to the root surface present code: https://cs.chromium.org/chromium/src/gpu/ipc/service/direct_composition_surface_win.cc?rcl=68520e01bfff88e3a01129e9f234760efb63ebcb&l=1031
►

Sign in to add a comment