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

Issue 659935 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Weird flickering of content is seen after opening 'system information' overlay.

Reported by vku...@etouch.net, Oct 27 2016

Issue description

Chrome Version: 56.0.2902.0 (Official Build) 22203b32bdae9236d23cc89e70772721315f2d1f-refs/heads/master@{#427892} (32/64-bit)
OS:Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.10.5, 10.11.4)

What steps will reproduce the problem?
(1)Launch chrome and navigate to chrome://md-settings/help
(2)Click on 'report an issue' link button, click on 'system information' and observe the overlay.

Actual: Weird flickering of content is seen after opening 'system information' overlay.

Expected: No such flickering should be seen after opening 'system information' overlay.

This is a regression issue broken in 'M56' and below is the manual regression range
Good Build: 56.0.2888.0
Bad Build:  56.0.2900.0 

 
Actual_settings.mp4
572 KB View Download
Expected_settings.mp4
455 KB View Download

Comment 1 by vku...@etouch.net, Oct 27 2016

Labels: hasbisect
Owner: dschuyler@chromium.org
Status: Assigned (was: Unconfirmed)
Below is the CL:
https://chromium.googlesource.com/chromium/src/+log/56.0.2888.0..56.0.2900.0?pretty=fuller&n=10000
(Unable to narrow down the range via tool since not able to reproduce the issue on chromium builds)

Suspecting: 426536 ?
Kindly help to re-assign, if your changes are not cause for this issue.
Labels: Proj-MaterialDesign-WebUI
Labels: Needs-Bisect
Could someone please do per-revision bisect? It actually invokes chrome instances instead of chromium.

Thank you!
Cc: rbasuvula@chromium.org
Labels: -Needs-Bisect hasbisect-per-revision
Owner: afakhry@chromium.org
Using the per-revision bisect providing the bisect results,
Good build: 56.0.2888.0 (Revision: 424625).
Bad build:  56.0.2900.0 (Revision: 427219).

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

CHANGE-LOG URL:
---------------------------------------
https://chromium.googlesource.com/chromium/src/+log/e7d7de88544002f3e1fd427a91f2bbef2bb35fe2..18870e37b4186d6d68529965cac48023436855ab


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

@ afakhry : 
------------------
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.

Review-Url: https://codereview.chromium.org/2403503003




Status: WontFix (was: Assigned)
This is working as intended. We're now building the table row by row, instead of blocking the UI entirely to build the whole table at once.

The effect is not very obvious on Windows as there aren't a lot of sys info there. But to see the effect on Chrome OS, take a look at  issue 653968 . 

Sign in to add a comment