New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 738124 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
OOO until 2019-01-24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Evaluate turning on WebGL for Android O 1GB devices

Project Member Reported by aelias@chromium.org, Jun 29 2017

Issue description

An unintended result of expanding "low-end device mode" up to 1GB on Android O devices is that GPU and browser processes are now merged, and therefore WebGL is blacklisted because our WebGL crash/hang recovery system depends on the separate GPU process.  So if an Android N 1GB device gets upgraded to Android O, we'd strip away the WebGL feature, and additionally it would significantly decrease support % of WebGL on Android because 1GB devices are very popular.  See  http://crbug.com/689752  and  http://crbug.com/730306  for context.

Aside from potential stability and security problems in pathological cases, WebGL probably works OK on 1GB devices with GPU process merged.  We should double-check common WebGL content works OK on 1GB O devices, and consider changing the blacklist policy.
 

Comment 1 by boliu@chromium.org, Jun 29 2017

webgl is still enabled for in-process gpu, if robustness extensions is present and robustness extension reset strategy is lose context, I think? I didn't find a uma for reset strategy though

Sign in to add a comment