1630590 - Text glithcing randomly on Facebook and affecting browser interface as well

Status: RESOLVED WORKSFORME

(Core :: Graphics: WebRender, defect, P3)

Description

[Mihai Chereji]

Attachment: Screenshot 2020-04-16 at 12.49.10.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:77.0) Gecko/20100101 Firefox/77.0

Steps to reproduce:

Don't have clear STR as of now, but it has happened at least twice, generally after having the Facebook Tab open for a while.

Actual results:

Text glitches, similar to the ones described in this call for help:
https://mozillagfx.wordpress.com/2020/02/18/challenge-snitch-on-the-glitch-help-the-graphics-team-track-down-an-interesting-webrender-bug/

When the bug does hit, it affects parts of the browser interface as well.

I'm attaching a screenshot of the glitch, covering up more sensitive parts with black squares.

Expected results:

Text should be glitch free, tab names should be visible.

Comment 1

[Mihai Chereji]

Attachment: about.support

Comment 2

[Bert Peers [:bpeers]]

Thanks Mihai. It looks like the GPU is not on the list of supported devices, but webrender was force-enabled via about:config:

WEBRENDER:
opt-in by default: WebRender is an opt-in feature
available by user: Force enabled by pref
WEBRENDER_QUALIFIED:
blacklisted by env: No qualified hardware
WEBRENDER_COMPOSITOR:
disabled by default: Disabled by default
WEBGPU:
disabled by default: Disabled by default

The problem might go away if you set gfx.webrender.all: false. We still would want to fix it of course.

Comment 3

[Glenn Watson [:gw]]

Markus, could the following from the about:support be relevant here?

Failure Log
(#0): CP+[GFX1-]: Failed to allocate a surface due to invalid size (DTD) Size(17150,17150)
(#1): CP+[GFX1-]: Failed to allocate a surface due to invalid size (DTD) Size(17150,17150)

Comment 4

[Jessie [:jbonisteel] pls NI]

Just adding a note - have been trying to repro on my Mac today (10.13) no luck yet

Comment 5

[Firefox Bug Husbandry Bot]

Resetting severity to default of --.

Comment 6

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Comment 7

[Jessie [:jbonisteel] pls NI]

Curious if you are still experiencing this glitching at all?

Comment 8

[Markus Stange [:mstange]]

(In reply to Glenn Watson [:gw] from comment #3)

Markus, could the following from the about:support be relevant here?

Failure Log
(#0): CP+[GFX1-]: Failed to allocate a surface due to invalid size (DTD) Size(17150,17150)
(#1): CP+[GFX1-]: Failed to allocate a surface due to invalid size (DTD) Size(17150,17150)

Hard to say.

I'm going to resolve this bug because no further issues have been reported in the last three years.