Rendering issues several visual effects (blur etc.)
Reported by
gw.ml...@gmail.com,
May 8 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Example URL: https://facebook.ai/developers Steps to reproduce the problem: 1.) Use macOS 10.11.x (El Capitan) 2.) Visit https://facebook.ai/developers and watch the background on mouse movement. What is the expected behavior? Background should move fluid. (See screencast) What went wrong? Background animation shutters/lags. (See screencast) Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 66.0.3359.139 Channel: stable OS Version: OS X 10.11.6 Flash Version: Screencast: https://cl.ly/0W1w3f2y3r1e Works in Chrome 65, 66&67 are broken, Canary (68) works again.
,
May 8 2018
@ccameron, I think this might be a duplicate of a bug you've already fixed. The background animation is in a canvas element.
,
May 9 2018
Unable to reproduce this issue on reported version 66.0.3359.139 using Mac 10.13.3 and Mac 10.12.6. TE team do not have Mac 10.11.6 available for us to check. Hence checked the issue on browserstack.com by selecting El Capitan M65 build and issue is not reproducible there. Hence adding TE-HardwareDependency label. Thanks!
,
May 9 2018
Okay, your device that was tested, was a MacBook Air which has no GPU. My Device: - iMac 27 inch, End 2012 - 2,9 GHz i5-3470S - 8GB RAM - GPU: NVIDIA GeForce GTX 660M 512MB - OS X 10.11.6 Also attached 2 screencasts from browserstack with El Capitan and High Sierra for comparison.
,
May 15 2018
I see that in about:gpu on those machines, GPU rasterization is enabled on one and disabled on the other -- that will probably do it -- drawing lots of pixels every frame on the CPU is very painfully slow. We also made some of the CPU raster situations a bit better in 68. Chrome 67 has a high merge barrier now that it has branched, so I'm putting this as fixed cause it's doing better in 68 per the original bug.
,
May 17 2018
So I just installed the current Chrome Beta version - (67.0.3396.40) - And the issue is gone. Thanks for your contribution! |
||||
►
Sign in to add a comment |
||||
Comment 1 by viswa.karala@chromium.org
, May 8 2018