massive performance drain and incorrect text color with Galaxy Tab A 8.0

[clshortfuse]

I have a couple of client with a Galaxy Tab A 8.0 with the following user Agent:

Mozilla/5.0 (Linux; Android 9; SM-T387V) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.119 Safari/537.36

mapbox-gl-js version: v1.8.1

browser: Chrome v80 on Android

Steps to Trigger Behavior

1. Open any MapBox map (even samples)
2. Look at street labels.
3. On light styles, the text is white. On dark styles, the text is black. Both are unreadable due to lack of contrast.

Coincidentally, (or perhaps not), all users of the same device are experience massive battery drain and overheating. On my application, which uses custom symbols and uses requestAnimationFrame I can track lag related to this function:

On the sample, it straight up crashed Chrome when trying to pan. I'm assuming there's an infinite loop going on somewhere. I'll post screenshots in a few minutes.

[clshortfuse]

Running Chrome profiler, it seems setStencilMode may be the issue.
Or possible UniformMatrix4f

mapbox-gl-js/src/render/uniform_binding.js

Line 117 in 5bbfde0

set(v: Float32Array): void {

[clshortfuse]

[mourner]

This definitely looks like some kind of a GPU bug. Can you please also share the full output of the chrome://gpu page (e.g. to a gist)?

[mourner]

Also, can you try a few previous versions of GL JS to see if this is something present everywhere or only in some of the versions?

[clshortfuse]

I can say it goes as far back at v1.6.0, but I'd have to get my hands on one of the devices again to get the chrome://gpu output.

[kkaefer]

Note that there are several devices with that name from various years (2015, 2017, 2018, and 2019). The model number @clshortfuse posted indicates that it's the one from 2018, which has a Qualcomm MSM8917 Snapdragon 425 with an Adreno 308 GPU. We've had lots of issues with Adreno GPU over the years due to poor driver quality, so this issue fits the pattern.

[SuperPat45]

I have this bug too on my Nokia 2.1 with Android Go 10.

And as my smartphone doesn't have a lot of memory Chrome stops the execution of the javascript a few seconds after the display of the map

It has a Snapdragon 425.