Using ANGLE on Android causes corruption
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: jrmuizel, Unassigned)
References
(Blocks 1 open bug)
Details
From Geoff Lang:
App name: Firefox Browser: fast, private & safe web browser/ Package name: org.mozilla.firefox/ App version: 95.1.0
Repro steps:
-
Execute the app
-
Input text to search
-
Observe
Problem: App screen displays solid black color instead of valid content (sometimes displays white color)
We should be able to mock this to reproduce by adjusting is_angle here: https://github.com/servo/webrender/blob/20d2dd6b6135f65879182c0b99344507da37b23a/webrender/src/device/gl.rs#L1655
|
Reporter | |
Updated•4 years ago
|
|
||
Comment 1•4 years ago
|
||
I'm a bit confused here Jeff. Is this talking about running with the system graphics driver set to Angle? Can we get an about:support?
The is_angle variable only affects the upload PBO stride alignment. I forced it to true but it doesn't seem to make any difference on my Pixel 2.
|
|
Reporter | |
Comment 2•4 years ago
|
||
My understanding was this was ANGLE on top of Vulkan on Android. When forcing the rendering string to not contain ANGLE the corruption went away.
|
||
Updated•4 years ago
|
|
|
||
Updated•4 years ago
|
|
|
||
Comment 3•4 years ago
|
||
It would be useful to know what device this was on and if they're planning to ship with a renderer string containing ANGLE. ie will this come back to bite us in the future?
It's presumably an angle bug or the device's vulkan driver bug. But we wouldn't want to ship with it anyway.
|
|
||
Comment 4•4 years ago
|
||
I believe bug 1758678 is a case of this in the wild. Thankfully It seems like Samsung has overridden the renderer string for Firefox, so only 3rd party geckoview apps are affected.
I think I know how to fix it but I have ordered a device so I can test it first. I'll close this bug and keep 1758678 open since it has a bit more information.
Description
•