Issue metadata
Sign in to add a comment
|
WebGL don't render properly on older Android (4.4)
Reported by
danielgj...@gmail.com,
Jul 6 2017
|
||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Load a site with a WebGL context running (e.g https://pixijs.github.io/examples/#/demos/blendmodes.js) 2. Notice that the canvas is rendered black (or quickly flashes then turns black). What is the expected behavior? The WebGL context should render the content correctly. What went wrong? The canvas is rendered solid black. No errors in the console. The demo above renders correctly in previous versions of Chrome on the same hardware/OS. It also renders correctly in other browsers such as FireFox. Did this work before? Yes Not sure. Worked with the version that came with the device Chrome version: 59.0.3071.115 Channel: stable OS Version: 4.4 Flash Version: This was tested on the Samsung Galaxy Tab E (KitKat 4.4) running an updated Chrome (v59). Also tested on Canary (61) with the same results.
,
Jul 6 2017
Ligi, do we have one of these devices on which to reproduce?
,
Jul 6 2017
ramine@, can you check this?
,
Jul 6 2017
Tested on following devices with chrome stable 59.0.3071.125 Lenovo A6000 (LRX22G); Platform GPU: Adreno 306 Galaxy Tab 3(KOT49H)- 7" display Galaxy S2 Tablet (MMB29M)- 9.7" display Moto G 3rd Gen/ 6.0.0 Adreno 306 Samsung Galaxy J5: Adreno 306 Not able to repro the issue.
,
Jul 6 2017
We also only see this on this particular device: Samsung Galaxy Tab E (the problem was reported to us by a third party, specifying the device as failing and we promptly got our hands on one and verified the issue). What we have discovered since this bug was filed is that some WebGL content do render while others fail (this one works: http://alteredqualia.com/three/examples/webgl_pasta.html). It seem to be sites running PixiJS-based content that fail while "pure" WebGL works. All demos on PixiJS site (e.g http://pixijs.github.io/examples/#/demos/render-texture-demo.js) fails. They all render fine (albeit a bit slow) in FireFox on the same device. Since it is the update of Chrome that causes the failure to happen I believe this bug is in the Chrome code base somewhere. It would be very unfortunate if this issue propagates to other devices in future updates of Chrome.
,
Jul 6 2017
Submitter, what are the contents of about:gpu from the device? If you can connect to it with Chrome DevTools and get us the ASCII contents that would be best. We're looking for all of the workarounds put in place, as well as the detailed driver information. Maybe we can find a similar device in house to test with. Unfortunately there are a ton of Android devices out there and as we evolve the code base things occasionally regress on older ones. We try to test on a range of newer devices though.
,
Jul 11 2017
,
Jul 11 2017
,
Jul 11 2017
,
Jul 11 2017
,
Sep 6 2017
How do one get the ASCII contents of the about:gpu page? I can't seem to find any way to save the page or copy the contents. We now have received reports of other devices with 4.4.X failing in Chrome 59 and 60. So it seems it is no longer limited to a particular device model. PS. Sorry for the late reply.
,
Sep 6 2017
This looks like a Samsung Galaxy Tab E. Ligi, do we have one of these devices in house? |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by schenney@chromium.org
, Jul 6 2017