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

Issue 755859 link

Starred by 2 users
Status: Duplicate
Merged: issue 755862
Owner:
sadrul@chromium.org
Closed: Aug 2017
Cc:
█ abdulsyed@chromium.org
ajha@chromium.org
gov...@chromium.org
nyerramilli@chromium.org
rbasuvula@chromium.org
ligim...@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 0
Type: Bug-Regression



Sign in to add a comment

Regression : Browser window turns black after restoring browser.

Reported by avsha...@etouch.net, Aug 16 2017 
Chrome version : 62.0.3187.0 (Official Build) 1066a02fc3eda664375a59a5962ccffa0e28c81f-refs/heads/master@{#494644} 64 bit
OS : Windows (7,8,10)

What steps will reproduce the problem?
1. Install #62.0.3187.0 clang build and launch it.
2. Minimize browser and restore it.
3. Observe.

Actual Result : Tab turns black after restoring browser window.

Expected Result : Tab should not turn black

This is a regression issue broken in ‘M-62’, below is the manual regression range and will soon other info.
Good build : 62.0.3186.0
Bad build : 62.0.3187.0

Comment 1 by avsha...@etouch.net, Aug 16 2017

Summary: Regression : Browser window turns black after restoring browser. (was: Regression : Tab turns black after restoring browser window.)
Actual_Result.mp4
1.7 MB View Download
Expected_Result.mp4
1.6 MB View Download

Comment 2 by avsha...@etouch.net, Aug 16 2017 

Note : Above issue is not reproducible on Mac(10.11.6, 10.12.3, 10.12.5) & Linux(14.04 LTS) OS using latest chrome canary #62.0.3187.0 and will soon update bisect info.

Comment 3 by rbasuvula@chromium.org, Aug 16 2017

Cc: gov...@chromium.org abdulsyed@chromium.org ligim...@chromium.org ajha@chromium.org
Labels: -Pri-1 hasbisect-per-revision ReleaseBlock-Dev Pri-0
Owner: sadrul@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build:62.0.3186.0(Revision:494273).
Bad build:62.0.3187.0(Revision:494644).

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

CHANGE-LOG URL:
---------------
https://chromium.googlesource.com/chromium/src/+log/aa32c7d6e682fb0f27ba3d8389af082a306a2c10..e0466cee3aa3f9f937fe0e515899ae808929ffb3

From the CL above, assigning the issue to the concern owner

@sadrul: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Reviewed-On:https://chromium-review.googlesource.com/614700
Note :Windows specific issue and Able to reproduce in latest Canary #62.0.3187.0
Adding Release Block-Dev for this issue.Please remove if not the case.

Comment 4 by ajha@chromium.org, Aug 16 2017

Mergedinto: 755862
Status: Duplicate (was: Assigned)
This looks to have the same root cause and regression range as  Issue 755862 , hence merging into that as sadrul@ has already started working on there.
►

Sign in to add a comment