Android Pixel8 displaying rendering artifacts
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: dbaker, Assigned: jnicol)
References
Details
Attachments
(7 files)
|
27.13 KB,
text/plain
|
Details | |
|
302.72 KB,
image/png
|
Details | |
|
936.92 KB,
image/png
|
Details | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-release+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
|
29.64 KB,
image/jpeg
|
Details |
Seeing issues like rounded buttons or labels not being displayed properly. When using whereby.com rednering artifacts are all over during a call.
Setup:
- Using Pixel 8 Pro
STR:
- Navigate to various sites and occasionally elements are not rendered correctly.
- Use whereby.com and join a call
| Reporter | ||
Comment 1•2 years ago
|
||
| Reporter | ||
Comment 2•2 years ago
|
||
| Reporter | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 3•2 years ago
|
||
I suspect this is the same as bug 1787520 and we just need to apply the same workaround to the new GPUs. (And I'll make it try to catch future GPUs too so we don't get bitten by this again)
| Assignee | ||
Comment 4•2 years ago
|
||
We had previously encountered a driver bug on Mali Valhall GPUs where
invalidating render targets once they are no longer required results
in rendering artefacts. This invalidation was purely an optimization,
which probably doesn't help much on Mali architecture anyway, so we
can workaround the bug by skipping the invalidation. See bug 1787520
for details.
The latest Mali Valhall GPUs are also affected. This patch therefore
applies the workaround to all "Mali-G" models apart from a list of
known working ones. This means we will avoid hitting this issue again
when the next generation of GPUs are released. Once ARM move on to the
next family we can see whether it is still affected and update the
code accordingly if required.
| Assignee | ||
Comment 5•2 years ago
|
||
Hi Dan, would you be able to install this APK and check whether you can still reproduce the bug in the Geckoview Example app that installs?
| Assignee | ||
Comment 6•2 years ago
|
||
Comment on attachment 9364453 [details]
Bug 1865224 - Avoid invalidating render targets on more Mali GPUs. r?#gfx-reviewers
Beta/Release Uplift Approval Request
- User impact if declined: Rendering glitches on some Android devices (including Pixel 8 and Pixel 8 Pro)
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Applies a workaround to some additional GPUs. The workaround is already being used on similar devices without issues.
- String changes made/needed:
- Is Android affected?: Yes
| Reporter | ||
Comment 8•2 years ago
|
||
I was able to test the APK with whereby and did not see an issue with rendering artifacts.
| Assignee | ||
Comment 9•2 years ago
|
||
We had previously encountered a driver bug on Mali Valhall GPUs where
invalidating render targets once they are no longer required results
in rendering artefacts. This invalidation was purely an optimization,
which probably doesn't help much on Mali architecture anyway, so we
can workaround the bug by skipping the invalidation. See bug 1787520
for details.
The latest Mali Valhall GPUs are also affected. This patch therefore
applies the workaround to all "Mali-G" models apart from a list of
known working ones. This means we will avoid hitting this issue again
when the next generation of GPUs are released. Once ARM move on to the
next family we can see whether it is still affected and update the
code accordingly if required.
Original Revision: https://phabricator.services.mozilla.com/D194063
Updated•2 years ago
|
| Assignee | ||
Comment 10•2 years ago
|
||
We had previously encountered a driver bug on Mali Valhall GPUs where
invalidating render targets once they are no longer required results
in rendering artefacts. This invalidation was purely an optimization,
which probably doesn't help much on Mali architecture anyway, so we
can workaround the bug by skipping the invalidation. See bug 1787520
for details.
The latest Mali Valhall GPUs are also affected. This patch therefore
applies the workaround to all "Mali-G" models apart from a list of
known working ones. This means we will avoid hitting this issue again
when the next generation of GPUs are released. Once ARM move on to the
next family we can see whether it is still affected and update the
code accordingly if required.
Original Revision: https://phabricator.services.mozilla.com/D194063
Updated•2 years ago
|
Comment 11•2 years ago
|
||
Uplift Approval Request
- String changes made/needed: N/A
- Risk associated with taking this patch: Low
- Steps to reproduce for manual QE testing: N/A
- Is Android affected?: yes
- Explanation of risk level: Applies a workaround to some additional GPUs. The workaround is already being used on similar devices without issues.
- Needs manual QE test: no
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- User impact if declined: Rendering glitches on Android devices, including Pixel 8 and Pixel 8 Pro
Comment 12•2 years ago
|
||
Uplift Approval Request
- Is Android affected?: yes
- Steps to reproduce for manual QE testing: N/A
- String changes made/needed: N/A
- Risk associated with taking this patch: Low
- Fix verified in Nightly: no
- User impact if declined: Rendering glitches on Android devices, including Pixel 8 and Pixel 8 Pro
- Code covered by automated testing: yes
- Explanation of risk level: Applies a workaround to some additional GPUs. The workaround is already being used on similar devices without issues.
- Needs manual QE test: no
Updated•2 years ago
|
Updated•2 years ago
|
Comment 13•2 years ago
|
||
| bugherder | ||
Comment 15•2 years ago
|
||
Comment on attachment 9364542 [details]
Bug 1865224 - Avoid invalidating render targets on more Mali GPUs.
Approved for 121.0b2.
Updated•2 years ago
|
Comment 16•2 years ago
|
||
| uplift | ||
Comment 17•2 years ago
•
|
||
I tried reproducing this issue using a Google Pixel 7 (Android 14).
Rendering of the elements is correct on the tested device.
Builds tested:
- Nightly 121.0a1 (2023-11-16).
- latest Nightly 122.0a1 (2023-11-23).
- latest Beta 121.0b2.
- Google Chrome.
Since I didn't reproduce the issue with earlier builds, and there was no manual QE testing needed, I won't mark this ticket as verified.
Comment 18•2 years ago
|
||
Comment 19•2 years ago
|
||
Comment on attachment 9364540 [details]
Bug 1865224 - Avoid invalidating render targets on more Mali GPUs.
Approved for Fenix/Focus/Klar 120.0.1.
Updated•2 years ago
|
Comment 20•2 years ago
|
||
| uplift | ||
Description
•