1776695 - Graphical issues on specific device

Status: RESOLVED INACTIVE

(Core :: Graphics: WebRender, defect)

Description

[Sören Hentzschel]

Attachment: about:support

In the Firefox support one user reported graphical issues and flickering since the update from Firefox 93 to 94. The issue is still present in Firefox 101.0.1 but not with disabled hardware acceleration.

The user told us that she found another user with the same laptop (Lenovo Ideapad 5-15ITL05 82FG005TGE) and the same issue with Firefox. So maybe related to the graphics card and/or driver?

I asked her to run mozregression and that gave us the following regression range:

https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=9476346a48fa84b35b7d505a84048db17d0d726c&tochange=a6d7f0da2513b78fce91dd35c2ea0495a6e6facd

From these three Bugzilla tickets, I guess only bug 1729241 makes sense? Glenn, I needinfo'ed you as author of the patches in bug 1729241. Do you think it's possible that the issue is caused by these changes?

I attached the about:support information from the affected user.

Comment 1

[Sören Hentzschel]

Attachment: screenshot

Screenshot from the affected user (look at the tabs).

Comment 2

[Sören Hentzschel]

Attachment: screenshot

Screenshot from the affected user (look at the right side of the content area, compare with screenshot 1).

Comment 3

[Glenn Watson [:gw]]

That patch shouldn't change anything that is specific to a graphics driver / GPU, it should be platform-independent changes only. Though, it's always possible with a driver bug that an unrelated change might expose something like this.

It's likely that we'd need to reproduce this locally to be able to find the root cause and fix.

Comment 4

[Sören Hentzschel]

Is there anything the affected user can try to help find the cause? Like disabling one of the many options in about:config to see if it's related to a certain graphics/webrender feature?

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:gw, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 6

[Glenn Watson [:gw]]

Perhaps try disabling gfx.webrender.compositor (browser restart is required) and see if that makes a difference?

Comment 7

[Sören Hentzschel]

I asked the user to change it but in the meantime the user updated the driver from version 27.20.100.9168 to version 30.0.100.9864 and that solved the issue.

It was initially unclear whether this driver could be installed at all because the user uses Windows 10 and the driver was only offered for Windows 11, but according to the manufacturer of the device, this should not be a problem.

I leave it to you to either do something for older drivers or to just close this issue.

Comment 8

[Glenn Watson [:gw]]

aosmond, jrmuizel, thoughts on what we should do for this broken driver?

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

Based on comment #0, this bug contains a bisection range found by mozregression. However, the Regressed by field is still not filled.

:eeejay, since you are the author of the changes in the range, if possible, could you fill the Regressed by field and investigate this regression?

For more information, please visit auto_nag documentation.