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

Issue 625046 link

Starred by 5 users

Issue metadata

Status: Duplicate
Merged: issue 625076
Owner:
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression

Blocking:
issue 624991



Sign in to add a comment

Regression: Black screen is observed after opening a maximized window.

Reported by rk...@etouch.net, Jul 1 2016

Issue description

Chrome Version: 53.0.2785.0 Revision 68623971be0cfc492a2cb0427d7f478e7b214c24-refs/heads/master@{#403382}
OS: Windows 10

What steps will reproduce the problem?

(1) Launch chrome, open incognito window and observe 
or
(1) Launch chrome, open NTP and restart chrome using chrome://restart and observe.
    
Black screen is observed after opening incognito window.

Black screen should not seen after opening incognito window.

This is a regression issue, broken in 'M-53' ,will soon update the other info

 

 

Comment 1 by rk...@etouch.net, Jul 1 2016

Labels: Proj-Windows10 hasbisect
Owner: robliao@chromium.org
Status: Assigned (was: Unconfirmed)
Good Build: 53.0.2784.0
Bad Build: 53.0.2785.0

Narrow Bisect:
https://chromium.googlesource.com/chromium/src/+log/50d0615528c167f0dd996dc03598590bfbb6d69f..840bb0f5eda052f9d0da148ced3a04610c4dc02d?pretty=fuller&n=100

Suspecting: r403329

Note: Issue is not seen on windows(7,8),Mac and Linux
Actual_blackscreen.mp4
293 KB View Download
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 1 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: ReleaseBlock-Stable
Able to reproduce the issue on Windows.
Adding RB Labels as this is a recent Regression. Please remove if not required.
Thank You.
This is not repro on me on 53.0.2785.0 Windows 10. What is your system configuration?
Labels: -M-54 M-53
Ah, got it. The window must be maximized for this to repro.
Status: Started (was: Assigned)
Investigating.
Summary: Regression: Black screen is observed after opening a maximized incognito window. (was: Regression: Black screen is observed after opening incognito window.)
Summary: Regression: Black screen is observed after opening a maximized window. (was: Regression: Black screen is observed after opening a maximized incognito window.)
Incognito is not necessary. Launching as maximized causes this. Revert is underway.
Project Member

Comment 10 by bugdroid1@chromium.org, Jul 1 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1c28de990fa24222973d9b462ee7eab89cf896e1

commit 1c28de990fa24222973d9b462ee7eab89cf896e1
Author: robliao <robliao@chromium.org>
Date: Fri Jul 01 17:05:33 2016

Revert of Enable Per-Monitor Support for Windows 10 (patchset #3 id:40001 of https://codereview.chromium.org/2114503002/ )

Reason for revert:
Causes maximized incognito windows to render blank.

Original issue's description:
> Enable Per-Monitor Support for Windows 10
>
> This allows Chrome to render at the native resolution on each display on
> Windows 10.
>
> BUG= 426656 , 624672 
>
> Committed: https://crrev.com/c110f1855d378172bcb74e0c26640bfc0d35d02d
> Cr-Commit-Position: refs/heads/master@{#403329}

TBR=thestig@chromium.org,scottmg@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG= 426656 , 624672 , 625046 

Review-Url: https://codereview.chromium.org/2115963002
Cr-Commit-Position: refs/heads/master@{#403472}

[modify] https://crrev.com/1c28de990fa24222973d9b462ee7eab89cf896e1/chrome/app/chrome_exe_main_win.cc

Blocking: 624991
Mergedinto: 625076
Status: Duplicate (was: Started)
Cc: jbau...@chromium.org
Status: Started (was: Duplicate)
Reopening for the merge.
Labels: Merge-Request-53
Labels: -Merge-Request-53 Merge-Approved-53
Approving merge of revert to M53 branch 2785 after discussing with robliao@. It is a pretty safe revert.
Project Member

Comment 16 by bugdroid1@chromium.org, Jul 1 2016

Labels: -merge-approved-53 merge-merged-2785
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/87d5cd10e2b9946ec8d33798268b07b336574e35

commit 87d5cd10e2b9946ec8d33798268b07b336574e35
Author: Robert Liao <robliao@chromium.org>
Date: Fri Jul 01 23:44:16 2016

Revert of Enable Per-Monitor Support for Windows 10 (patchset #3 id:40001 of https://codereview.chromium.org/2114503002/ )

Reason for revert:
Causes maximized incognito windows to render blank.

Original issue's description:
> Enable Per-Monitor Support for Windows 10
>
> This allows Chrome to render at the native resolution on each display on
> Windows 10.
>
> BUG= 426656 , 624672 
>
> Committed: https://crrev.com/c110f1855d378172bcb74e0c26640bfc0d35d02d
> Cr-Commit-Position: refs/heads/master@{#403329}

TBR=thestig@chromium.org,scottmg@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG= 625046 

Review-Url: https://codereview.chromium.org/2115963002
Cr-Commit-Position: refs/heads/master@{#403472}
(cherry picked from commit 1c28de990fa24222973d9b462ee7eab89cf896e1)

Review URL: https://codereview.chromium.org/2119983003 .

Cr-Commit-Position: refs/branch-heads/2785@{#4}
Cr-Branched-From: 68623971be0cfc492a2cb0427d7f478e7b214c24-refs/heads/master@{#403382}

[modify] https://crrev.com/87d5cd10e2b9946ec8d33798268b07b336574e35/chrome/app/chrome_exe_main_win.cc

Status: Duplicate (was: Started)
Duping back to the primary.

Sign in to add a comment