New issue
Advanced search Search tips

Issue 812126 link

Starred by 1 user
Status: Fixed
Owner:
dmazz...@chromium.org
Closed: Feb 2018
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Text of chrome://kill page is not seen after opening dev tools window.

Reported by db...@etouch.net, Feb 14 2018 
Chrome Version: 66.0.3346.0 Revision 21b7a819b0547b7ade4252a162cc4c98ba29f149-refs/heads/master@{#536238}(32/64 bit)
OS: Windows(7,8,8.1,10), Linux(14.04 LTS)

What steps will reproduce the problem?
(1) Launch chrome, navigate to chrome://version and open Dev tools window on it.
(2) Then type chrome://kill in omnibox and observe

Actual: Text of chrome://kill page is not seen.

Expected: Text of chrome://kill page should seen.

This is a regression issue, broken in 'M66', will soon update the other info:

Comment 1 by db...@etouch.net, Feb 14 2018

Labels: ET-MUM-Reported hasbisect
Owner: dmazz...@chromium.org
Status: Assigned (was: Unconfirmed)
Good Build:66.0.3344.0 (Revision : 535593)
Bad Build:66.0.3345.0  (Revision : 536026)

Narrow Bisect:
https://chromium.googlesource.com/chromium/src/+log/b418ba9fb4875c53ef63b684e283699f2cfcd4e1..a60e495ea2084539e350f51125843dc207868d58?pretty=fuller&n=100

Suspect: r535735 ?

@Dominic Mazzoni: 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.

Note: 1.Unable to bisect using bisect-per-revision script hence proving suspect from narrow bisect.
      2. Above issue is not seen on Mac(10.12.6,10.13.1,10.13.2)OS.

Comment 2 by db...@etouch.net, Feb 14 2018

Labels: RegressedIn-66 FoundIn-66 Target-66
Actual_Kill.mp4
341 KB View Download
Expected_Kill.mp4
350 KB View Download

Comment 3 by rbasuvula@chromium.org, Feb 15 2018

Labels: ReleaseBlock-Stable
Adding release blocker label for this issue.Please reduce priority or remove if not the case.

Thank You!

Comment 4 by dmazz...@chromium.org, Feb 15 2018

Status: Started (was: Assigned)
Project Member

Comment 5 by bugdroid1@chromium.org, Feb 21 2018 

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

commit 03a4f1efe8af5b3aaf2f576e2534fad34593059e
Author: Dominic Mazzoni <dmazzoni@chromium.org>
Date: Wed Feb 21 23:45:58 2018

Ensure sad tab is drawn even when dev tools is showing.

Bug:  812126 
Change-Id: If5ceea0c70e8233926089e72898a0cde49eaebdc
Reviewed-on: https://chromium-review.googlesource.com/923114
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538257}
[modify] https://crrev.com/03a4f1efe8af5b3aaf2f576e2534fad34593059e/chrome/browser/ui/views/sad_tab_view.cc

Comment 6 by dmazz...@chromium.org, Feb 22 2018

Status: Fixed (was: Started)

Comment 7 by db...@etouch.net, Feb 22 2018 

Update:

Above issue is fixed on  Windows(8.1,10) and Linux(14.04 LTS) OS using Canary build #66.0.3352.0.

Unable to check this issue on win(7,8) OS using Canary build #66.0.3352.0(64 bit) as builds are getting crashed as per Issue id:814641, but issue is fixed on win(7,8) OS using canary #66.0.3352.0(32 bit)


Thank you.
Actual_Fix.mp4
312 KB View Download
►

Sign in to add a comment