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

Issue 674110 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Regression:Unwanted white patch is seen after pinch to zoom in/out in "www.universalpictures.com"

Reported by adha...@etouch.net, Dec 14 2016

Issue description

Chrome Version:57.0.2951.0 (Official Build) eaf56dab37408dfad3152c5e00092ab99f775273-refs/heads/master@{#438385}-32/64 bit
OS: Windows 10(Touch device)

TEST URL:https://www.universalpictures.com/movies/a-dogs-purpose

What steps will reproduce the problem?
(1)Launch chrome and navigate to the above url.
(2)Scroll down the page and pinch to zoom in/out.(Kindly refer the video)
(3)Observe.

Actual:Unwanted white patch is seen after pinch to zoom in/out.

Expected:No such white patch should be seen after pinch to zoom in/out.

This is a Regression issue broken in M-57,below is the Narrow bisect info:
https://chromium.googlesource.com/chromium/src/+log/e67718d152e7390d6dcbc33209367becd8aa6ed6..b25dd7e750dd25ee51f49d463ddce3eea3efc665?pretty=fuller&n=100

Suspecting:r433130?

Good build:56.0.2924.0
Bad build:57.0.2926.0

Kindly help to re-assign if your change is not the cause for this issue.

Note: This touch device specific issue, same works fine via mouse click
 
Actual result.mp4
1.2 MB View Download
Expected result.mp4
1.2 MB View Download

Comment 1 by msw@chromium.org, Dec 14 2016

Labels: wron Needs-Bisect
Owner: ----
Status: Untriaged (was: Assigned)
My change is certainly unrelated, and I don't see anything suspicious in that range. I would guess that the regression range is incorrect, marking untriaged for help from blink/touch folks, and tagging Needs-Bisect to double check the regression range.

Comment 2 by tkent@chromium.org, Dec 15 2016

Components: -Blink Internals>Compositing

Comment 3 by adha...@etouch.net, Dec 15 2016

Labels: -Needs-Bisect -wron
Owner: sashab@chromium.org
Status: Assigned (was: Untriaged)
Above issue is reproducible on latest canary version i.e 57.0.2952.0

Re-bisected the above issue ,below is the Narrow bisect range:
https://chromium.googlesource.com/chromium/src/+log/7abf8d02361194aaf12bc8d962d5dfd7832365e0..813fe9380b32017f9187b9fb1172354bd2763d65?pretty=fuller&n=10000

Suspecting:r433044?

Kindly help to re-assign if your change is not the cause for this issue.

Comment 4 by sashab@chromium.org, Dec 15 2016

Labels: Needs-Bisect
Owner: ----
My change is just a rename so not related to this.

I actually have no idea who's patch this could be. Could we get a narrower regression range please?
Labels: -hasbisect -Needs-Bisect hasbisect-per-revision
Owner: dcheng@chromium.org
Re-bisected the above issue ,below is the Narrow bisect range:

Good build: 54.0.2840.0 (Revision: 410913).
Bad build: 55.0.2841.0 (Revision:414854).

CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/f0c41ef01d1ef97872bb0f97d8c0e0a6d0884baf..5544c19b4252cbf65eea6894d55b2ed486957079

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

dcheng@  could you please look into this issue if it is related to your change,else please help us in finding the appropriate owner for this issue.

Thanks.


Comment 6 by dcheng@chromium.org, Dec 16 2016

Cc: dcheng@chromium.org
Owner: wangxianzhu@chromium.org
I don't think it's my CL. How was the changelog URL derived? I get a very different list of CLs:
https://chromium.googlesource.com/chromium/src/+log/54.0.2840.0..55.0.2841.0?pretty=fuller&n=10000

I don't honestly know what's wrong here though. Maybe something with invalidations? I see https://chromium.googlesource.com/chromium/src/+/0a848fcd4d159ff31f30aa20f4c0d6fd7a6a4123 landed during this time, but I have no idea if it could cause the artifacts in question. +wangxianzhu, any ideas?
Cc: wangxianzhu@chromium.org
Labels: -hasbisect-per-revision Needs-Bisect
Owner: ----
Status: Available (was: Assigned)
My change is for spv2 only which is not enabled by default yet.

Perhaps another bisect is helpful to make sure the regression range is correct.
Cc: jmukthavaram@chromium.org
Labels: -Needs-Bisect

Thanks for the report.

Able to reproduce the issue on Win 10 (Touch screen machine) using Chrome Canary #57.0.2965.0,Stable #55.0.2883.87 and reported version-57.0.2951.0.

This is non-regression issue which is existing from M35 builds onwards.

Observed Unwanted white patch is seen after pinch to zoom in/out.

Please find the attached screenshot for reference.
674110.mp4
5.1 MB View Download

Comment 9 by ajuma@chromium.org, Jan 21 2017

Labels: -Type-Bug-Regression Type-Bug
Status: WontFix (was: Available)
The white patches are checkerboarding, which is the expected behavior when we haven't finished rastering a portion of the page.

If checkerboarding had suddenly become worse on this page, that would be something to investigate, but according to #8 this has been happening since M35. So I think we can close this.

Sign in to add a comment