Issue metadata
Sign in to add a comment
|
Chrome v64 produce Flickering artifacts in Three.js SoftwareRenderer
Reported by
user972...@gmail.com,
Jan 26 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36 Steps to reproduce the problem: 1. Visit https://threejs.org/examples/software_geometry_earth.html 2. Move the mouse and you may see a lot of flickering on the border, here is recored GIF: https://media.giphy.com/media/3ohs4pTqRWNCEq1noY/giphy.gif What is the expected behavior? No flikering artifacts What went wrong? The SoftwareRenderer examples by Three.js produce a lot of flickering artifacts when updated Chrome to v64. See this gif for better demonstration: https://media.giphy.com/media/3ohs4pTqRWNCEq1noY/giphy.gif I have opened an issue on Three.js github ( https://github.com/mrdoob/three.js/issues/13174 ) Some report it working fine, some have the same problems, this looks like browser bug so I opened this issue here. Did this work before? Yes Chrome v63 Chrome version: 64.0.3282.119 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 28.0 r0
,
Jan 29 2018
Able to reproduce the issue on chrome version 64.0.3282.119 using Windows-10. The issue is not seen on previous stable 63.0.3239.132 and latest dev 65.0.3225.18. As the issue got fixed on latest canary 66.0.3334.0, hence providing reverse bisect info to find where the fix has landed.
Note: The issue is not seen on Mac 10.13.1 and Ubuntu 14.04.
Reverse Bisect Info:
================
Bad build: 65.0.3322.0 Revision(529187)
Good Build: 65.0.3323.0 Revision()
You are probably looking for a change made after 529327 (known good), but no later than 529328 (first known bad).
https://chromium.googlesource.com/chromium/src/+log/ddbc1a049317170cd1e2477e0dd002ba5b6f00cb..d02bb8346f13117d4a81d1124a3aeeaaed83ae99
Reviewed-on: https://chromium-review.googlesource.com/864630
Note: Adding RB-Stable as it is a recent regression, feel free to remove if not applicable. As it is working fine in previous M63 stable and latest M65 dev hence adding label RegressedIn-64.
@xlai: Please confirm the issue and help in re-assigning if it is not related to your change and could you please confirm whether its safe to merge to M-64.
Thanks!
,
Jan 29 2018
My guess is that this is a duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=805605?
,
Jan 29 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Jan 27 2018Labels: Needs-Bisect Needs-Triage-M64