Issue metadata
Sign in to add a comment
|
Regression: Movement of the page is not smooth on chrome://settings after disabling hardware acceleration.
Reported by
aiman.an...@etouch.net,
Aug 8 2017
|
||||||||||||||||||||
Issue descriptionChrome Version: 62.0.3179.0(Official Build)b5b73b0139e1b065902ba751610210b6322c827f-refs/heads/master@{#492477} (64-bit). OS: MAC(10.11.6, 10.12.3, 10.12.5). Steps to Reproduce: 1. Launch chrome, go to chrome://settings/systems and disable hardware acceleration. 2. Relaunch Chrome, on chrome://settings keep on the resizing window and observe. Actual Result: Movement of the page is not smooth on chrome://settings after disabling hardware acceleration. Expected Result: Movement of the page should be smooth on chrome://settings after disabling hardware acceleration. This is Regression Issue broken in M-61 and will soon update the other bisect info. Manual Bisect Info: Good Build: 61.0.3156.0 Bad Build: 61.0.3158.0 Note: Above issue is MAC specific.
,
Aug 16 2017
My CL is chromeos specific, and not used by mac. I did take a quick look at the blame range, but couldn't tell which might be a culprit. I think someone should just run bisect.
,
Aug 17 2017
Note: Retested the above issue on latest canary 62.0.3188.0 on Mac OS and issue is very inconsistent. Change Log URL: https://chromium.googlesource.com/chromium/src/+log/61.0.3156.0..61.0.3158.0?pretty=fuller&n=10000 Providing manual bisect range: Good Build: 61.0.3156.0(486206) Bad Build: 61.0.3158.0(486952)
,
Aug 18 2017
,
Aug 18 2017
Note: Unable to provide Narrow Bisect since issue is very inconsistent on chromium builds, hence providing through CL. Change Log URL: https://chromium.googlesource.com/chromium/src/+log/61.0.3156.0..61.0.3158.0?pretty=fuller&n=10000 Suspecting: r486937 ? @Chris Harrelson: Could you please look into this issue, if it's related to your change? if not could you please help us to reassign this issue to the right owner.
,
Aug 23 2017
Hmm. Chris are you able to reproduce this? Is this worth fixing in your view?
,
Aug 23 2017
I can reproduce this. The resize is choppy enough to suggest that we're just timing out every time (and perhaps weren't in the past). Might be worth re-bisecting, cause I don't see anything suspicious in the blame list. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by aiman.an...@etouch.net
, Aug 8 2017Labels: hasbisect
Owner: osh...@chromium.org
Status: Assigned (was: Unconfirmed)