Open Bug 1741174 Opened 3 years ago Updated 2 years ago

[Bug]: rendering broken in 94.1.2 (Moto X - Adreno 320)

Categories

(Core :: Graphics, defect, P3)

Unspecified
Android
defect

Tracking

()

Tracking Status
firefox-esr91 --- unaffected
firefox94 + wontfix
firefox95 + wontfix
firefox96 + wontfix

People

(Reporter: petru, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression)

From github: https://github.com/mozilla-mobile/fenix/issues/22435.

Steps to reproduce

  1. go to a website eg. en.wikipedia.org
  2. scroll down the page

Expected behaviour

Text and images should be legible

Actual behaviour

Some images are corrupted or not drawn. Some text is replaced with incorrect characters (some not ASCII), sometimes overlapping. Scrolling backwards and forwards will change which text and images are rendered correctly, so after a while it may be possible to read the whole page.

Device name

Motorola Moto X

Android version

Android 5.1

Firefox release type

Firefox

Firefox version

94.1.2

Device logs

No response

Additional information

The same behaviour applies to Fennec 94.1.1. The previous release of Firefox and Fennec 93.1.0 work correctly.

Change performed by the Move to Bugzilla add-on.

See Also: → 1719280

I think Jamie managed to track this down in the github issue.

Severity: -- → S3
Priority: -- → P3

Not tracked down unfortunately, but did manage to confirm a (fairly surprising) regression range

Regressed by: 1730867
Has Regression Range: --- → yes
Summary: [Bug]: rendering broken in 94.1.2 → [Bug]: rendering broken in 94.1.2 (Moto X - Adreno 320)

Set release status flags based on info from the regressing bug 1730867

Changing the priority to p1 as the bug is tracked by a release manager for the current release.
See What Do You Triage for more information

Priority: P3 → P1

Hi Jamie, any updates on this?

Flags: needinfo?(jnicol)

I ordered a Moto X device, but it arrived running Android 4.4 and it cannot find the 5.0 update. So no luck there.

I've ordered a Nexus 4 instead, which has the same GPU and is easier to flash different android versions. Hopefully it will have a similar enough driver version to reproduce the issue.

Flags: needinfo?(jnicol)

Hi Jamie, any luck with the Nexus 4?

Flags: needinfo?(jnicol)

Unfortunately not. Nor with a Samsung Galaxy S4 or a Moto X as the original reporter had.

Flags: needinfo?(jnicol)

Tested steps using Fx97.1 on OnePlus 8 (Android 11), and could not reproduce.

Priority: P1 → P3
You need to log in before you can comment on or make changes to this bug.