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

Issue 773797 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 768134
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Chrome displays artifacts when using bootswatch's Slate theme

Reported by davidmcc...@gmail.com, Oct 11 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Example URL:
https://jsfiddle.net/Lf1cxo7f/

Steps to reproduce the problem:
1. Navigate to the JSFiddle above
2. Mouse over the four spans

What is the expected behavior?
The hovered span should become "active" and become lighter, but the background and rest of the heading should remain the same

What went wrong?
Blocky artifacts are displayed randomly, made worse by mouse movement

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes Chromium build 440007

Does this work in other browsers? Yes

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 27.0 r0

Also posted to StackOverflow with no response. https://stackoverflow.com/questions/46591972/seeing-blocky-artifacts-in-chrome

Not sure that Chromium build 440007 was the last version where it worked, but it definitely worked then. Versions after that started displaying large solid black blocks and then shortly after began showing the black artifacts it currently displays.
 
Chrome Artifacts.PNG
2.3 KB View Download
Labels: Needs-Triage-M61

Comment 2 by bokan@chromium.org, Oct 12 2017

Cc: bokan@chromium.org
Components: -Blink Internals>GPU
Could you try Chrome Canary and see if the issue still reproduces there?
Cc: amit@chromium.org krajshree@chromium.org brajkumar@chromium.org
Labels: -Type-Bug -Pri-2 M-63 hasbisect Pri-1 Type-Bug-Regression
Owner: liber...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce this issue on Win 10 with Chrome reported version 61.0.3163.100 and latest canary 63.0.3238.0 as per steps mentioned in C#0

Manual Bisect info:
Good Build :  59.0.3033.0 - revision - 455023
Bad Build :  59.0.3034.0 - revision - 455336

Note: Issue is not reproducible on Ubuntu 14.04 and Mac 10.12.6

Per-revision bisect invoked all good builds, hence providing chromium bisect changelog
You are probably looking for a change made after 455172 (known good), but no later than 455188 (first known bad).CHANGELOG URL:  https://chromium.googlesource.com/chromium/src/+log/e806d46df51009e8c254727b374873bc4379b1fb..4f4441915d7f7dee6dd36fcf3e06e743f5779e2c

Suspecting
https://codereview.chromium.org/2706653002

@liberato:Kindly take a look and please help us to reassign this issue to a right owner if not with respect to this change.

Thanks.!



sorry for the delay -- missed this one.  the change in c#3 is entirely code that's compiled only for android.  it's definitely not affecting win 10.  i'll try to narrow it down.

Comment 6 by vmi...@chromium.org, Oct 17 2017

Cc: ericrk@chromium.org
Labels: Needs-Feedback
Owner: bsalomon@chromium.org
Could you please attach a copy of the output from navigating to chrome://gpu ?

Suspecting Skia roll at https://chromium.googlesource.com/chromium/src/+/c4adf5ff6dc1cb76bd0fd956de3affeeb14f9060

Comment 7 Deleted

Gpu output file is attached
gpu.htm
55.3 KB View Download

Comment 9 by bsalo...@google.com, Oct 17 2017

Cc: robertphillips@chromium.org
I cannot reproduce this on Canary 64.0.3242.0.

I can reproduce on Stable 61.0.3163.100 but only after downgrading my NVIDIA driver to 353.62.

Rob, is it possible this is the D3D11 clear issue given the version of Canary that did repro in #3?
Mergedinto: 768134
Status: Duplicate (was: Assigned)
Indeed it is.

Sign in to add a comment