Issue metadata
Sign in to add a comment
|
WebGL seems to incorrectly detect the end of a frame
Reported by
lau...@mapbox.com,
Oct 10 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Load test case 2. Note the finished state of the initial frame 3. Click on the map once to trigger a new frame; see more content load What is the expected behavior? All loaded data is rendered in the frame when loading is finished. What went wrong? Data that is loaded isn't all rendered in the initially displayed frame. It seems Chrome is incorrectly detecting the end of a frame. I'm not sure whether or not this is related to https://bugs.chromium.org/p/chromium/issues/detail?id=773337 (sorry this test case couldn't be quite as minimized as that one). Based on our library code, the state of the screenshot I'm attaching is impossible to achieve in any complete frame (road layers that are being rendered and road layers that aren't being rendered are rendered from the same processed data). I'm also attaching a video that shows the complete frame rendered on click (on second render frame). It does not consistently end on the same part of the frame, but consistently stops rendering before a frame is complete. I'm on a 13" 2016 MacBook Pro with Intel Iris Graphics 550 1536 MB. When my colleague with a 15" Macbook Pro with AMD Radeon Pro 450 chip tries to reproduce this it looks more like https://bugs.chromium.org/p/chromium/issues/detail?id=773337, where the frame where the render finishes sometimes flickers and is replaced with an earlier frame (but is not necessarily as obviously the same bug as this…). Did this work before? Yes Chrome 60 Does this work in other browsers? Yes Chrome version: 61.0.3163.100 Channel: stable OS Version: OS X 10.12.6 Flash Version:
,
Oct 11 2017
Unable to reproduce the issue on the reported chrome version stable 61.0.3163.100 and on the latest canary 63.0.3236.0 using Mac 10.12.6. We have checked the issue on MacBook Air.(13-inch,Early 2014) with Intel HD Graphics 5000 1536MB Attaching the screencast of the same. Requesting someone from inhouse team to take a look at this if issue specific graphics are available. Thanks!
,
Oct 11 2017
I think this is the same problem as both Issue 773337 and Issue 769488 . Wasn't able to reproduce on a MacBook Air with Intel HD 5000 GPU and either Chrome Stable (61) or Canary (63). Could you please test with the Chromium continuous builds linked in https://bugs.chromium.org/p/chromium/issues/detail?id=773337#c4 and confirm that the problem was fixed at that point?
,
Oct 11 2017
Per feedback on Issue 773337 , this is the same problem as Issue 769488 . |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Oct 10 2017