Hello

Can you please recheck the URL? On Android One Plus One, navigating to the URL gives 'Error 404 -page cannot be found' but works on the desktop. Also, please provide Bugreport and logcat for your issue along with Video, if any.

We also require the contents of chrome://gpu on the affected device, for all GPU related reports. Please copy+paste or attach as a txt file.

- urls works here (desktop and mobile)
- attached the gpu.txt
- 

Deleted: gpu.txt 6.5 KB

gpu.txt 6.5 KB View Download

Deleted: androidoneplusone.jpg 53.6 KB

	androidoneplusone.jpg 53.6 KB View Download

Thank you for providing more feedback. Adding requester "ppolisetty@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

When looking at gpu.txt I realized you're testing on Chrome 57 with --enable-es3-apis. Chrome 57 has serious WebGL 2.0 issues on Android (which was why it did not enable WebGL 2.0 by default). Please re-test on Chrome 58, which should have just been released to stable. Or, use the beta, dev, or canary channel.

Please let us know if the issue persists.

Just tested on 58, 59, 60.
Still getting gpu render driver glitches

Thank you for providing more feedback. Adding requester "kainino@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

WebGL 2.0 is not supported on Chrome on Adreno 3xx series GPUs. Sorry I didn't notice this earlier when looking at your chrome://gpu.

General public users will not be able to use WebGL 2.0 at all on this device. We don't support explicitly enabling it in chrome://gpu.

For future reference, I'm able to reproduce on Nexus 7 2013, Adreno 320 (with --enable-es3-apis).

correction: explicitly enabling it in chrome://flags

Thanks for the anwser, clarifies a lot.

I guess there no ways to detect that case client-side ?

I'm not sure what case you're trying to detect. Any time a 'webgl2' context fails to create, it's because either the hardware or browser doesn't support it, or because the browser has disabled it (due to the hardware configuration, or a flags setting, etc). When 'webgl2' is unavailable you should always try to fallback to 'webgl' (1.0).

If you want to tell the user "your hardware isn't supported on this browser", then all you need to know is (1) the 'webgl2' context creation failed and (2) the browser version (e.g. is it chrome>=56, mobile chrome>=58, firefox>=51?)

Was wondering if we could detect "webgl2 force enabled by user" so that we fallback to webgl1.

No, I don't think that can be detected. However the number of users manually enabling webgl2 should be extremely close to zero.