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

Issue 655869 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Clear old workaround in Android to use client side arrays

Project Member Reported by zmo@chromium.org, Oct 14 2016

Issue description

These entries are more than three years old and I can't find a bug to connect to them. They lead to nasty work around in command buffer and now in ES3 we just don't want to support them anymore because ES3 we have much more buffer manipulation path than ES2 and to make everything work with these workarounds is a lot of work and bug prone.

Per discussion with @aelias, the plan is: remove them and see if we receive any complaints; then we know what the real issue is on which devices and figure out a way forward.

 

Comment 1 by aelias@chromium.org, Oct 14 2016

Cc: senorblanco@chromium.org bsalomon@chromium.org
This was introduced due to  http://crbug.com/178093 .  It seems to be a workaround for a Nexus 10 (Mali-T604) specific problem.  The Nexus 10 was a pretty crappy and unique device with all kinds of performance problems that only affected it, and as far as I'm concerned it's out of our support window (except in terms of causing it to actively crash), so if it's the only reason, I'm fine with the removal.  bsalomon@/senorblanco@, any thoughts?

Comment 2 by aelias@chromium.org, Oct 14 2016

I guess it also includes PowerVR like Nexus S and Galaxy Nexus.  Those are out of our effective support window, too.

The if "ARM" condition for a Mali-T604 specific problem sounds way too broad, also.
Perhaps we should test on a more recent Mali (e.g. Exynos S7) to make sure we don't regress performance.

Sign in to add a comment