Same Problem here on Chrome 61 in Chrome 60 its okay, see Picture.

Deleted: example.PNG 49.5 KB

	example.PNG 49.5 KB View Download

I can't reproduce this on Linux or Mac. Perhaps it's Windows-specific,
will test there.

Also can't reproduce this on Windows in GPU or software mode.

Bug reporter: could you please past the contents of navigating to
"about:gpu" here?

Here is my "about:gpu".

Deleted: gpu.html 158 KB

gpu.html 158 KB View Download

Thank you for providing more feedback. Adding requester "chrishtr@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Hello i have record a video for this Problem.

Reproduce on this example
https://runner.telerik.io/fullscreen/uJIwi

Deleted: Sep 12 2017 8-33 AM.webm 628 KB

	Sep 12 2017 8-33 AM.webm 628 KB View Download

Hey, I've got some new infos. The problem only occurs with Intel graphics cards. There are no problems with Geforce and ATI graphics cards.

Able to reproduce the issue on Windows 10 Lenovo laptop using chrome #61.0.3163.79 as per the below URL.
https://jsfiddle.net/wrbddLLd/
Observed some rendering issue while resizing the page.
Manual bisect info:
-----------------
Good-60.0.3094.0-Revision-470111
Bad-60.0.3095.0-Revision-470437

Change log:
-----------
https://chromium.googlesource.com/chromium/src/+log/60.0.3094.0..60.0.3095.0?pretty=fuller&n=10000

Unable to provide bisect for the above CL range with old and new scripts,marking it as Untriaged. Could some one from dev team please look into this issue.

Please find the attached screencast for reference.

Note: No issue observed on Mac, Ubuntu & Windows 7,10 (Desktops)
Thanks..!

Deleted: 763767.mp4 3.0 MB

	763767.mp4 3.0 MB View Download

jmukthavaram@, are you able to narrow the bisect further using the bisect-builds script? I'm not seeing an obvious suspect in the range above, so a narrower range would be helpful. See https://www.chromium.org/developers/bisect-builds-py. Thanks!

In the production environment tentatively I found out a way to avoid this bug.
That is to use "filter" and "transform: translateZ(0)" together.

Here is the sample code.
https://jsfiddle.net/uqf9hcvk/

We're having problems extremely similar to this, where noise (graphics buffer corruption?) appears on rendering a large div with opacity, which started with 61 but was fine prior to that.

Our own investigation has also identified use of Intel HD Graphics as a factor, since the problem doesn't manifest if hardware acceleration is disabled, or if it is configured to use the NVIDIA GPU instead of the Intel graphics.

These same conditions seem to apply to the repro case above, although it takes a couple refreshes.

about:gpu attached

Deleted: gpu.htm 52.6 KB

gpu.htm 52.6 KB View Download

I also tried a couple things listed in other similar opacity-rendering issue tickets - disabling gpu rasterization or running with --disable-d3d11 also suppress the problem.

https://bugs.chromium.org/p/chromium/issues/detail?id=768207
https://bugs.chromium.org/p/chromium/issues/detail?id=768134

Enne/Brian, is this related to the other opacity bugs that are floating around?

Yes, this seems like a duplicate of  issue 755871 .

This bug is not reproduce in Chrome 62.
Thank you.