1729900 - Firefox browser window flickering on nvidia 470.63.01(GT 710) / Xfce

Status: RESOLVED WORKSFORME

(Core :: Graphics: WebRender, defect)

Description

[Mubashshir]

Attachment: ffbug-2021-09-09_18.54.40.webm

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:92.0) Gecko/20100101 Firefox/92.0

Steps to reproduce:

1. Start firefox.
2. Suffer.

Actual results:

Window Randomly becomes transparent(with window compositor running)/black(w/o window compositor), either whole window or a part of window, Doesn't happen to popup/menu/dialogs. Setting gfx.webrender.force-disabled to true doesn't work

Expected results:

Window should be rendered properly

Comment 1

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

The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Darkspirit]

Thanks for the report!
Please open about:support, click on "Copy text to clipboard" and paste it here. Which window manager are you using?

Comment 3

[Mubashshir]

Attachment: Original profile

My Setup:
DE: Xfce 4.16
WM: Xfwm4(w/o compositor)
Compositor: Picom vgit-ee7d9

Comment 4

[Mubashshir]

Attachment: Clean profile

Comment 5

[Darkspirit]

1. Can this be fixed by starting Firefox with MOZ_X11_EGL=1 environment variable? $ MOZ_X11_EGL=1 firefox (This env var requires nvidia driver >=470 which you have. It would also be interesting to know if it still crashes on your non-XWayland X11.)
2. Can this be fixed by setting gfx.webrender.software to true and restarting Firefox?

Comment 6

[Mubashshir]

1. Doesn't fix completely(reduces flicker)
2. Fixes completely(w/o applying 1)

Comment 7

[Darkspirit]

(In reply to Mubashshir from comment #6)

1. Doesn't fix completely(reduces flicker)

(offtopic, but interesting) Please attach about:support of it ($ MOZ_X11_EGL=1 firefox). Are you able to set a bookmark, open the main menu and context menu without a crash, does it just work fine?

2. Fixes completely(w/o applying 1)

Please try to find a regression range, if possible. At the end, you should get a pushlog URL:
pip3 install mozregression
mozregression --good 2021-02-01 --bad 92 --pref gfx.webrender.all:true

Comment 8

[Mubashshir]

Attachment: offtopic: MOZ_X11_EGL

(offtopic, but interesting) Please attach about:support of it ($ MOZ_X11_EGL=1 firefox). Are you able to set a bookmark, open the main menu and context menu without a crash, does it just work fine?
Works fine, except for the flickers.

Comment 9

[Darkspirit]

(In reply to Mubashshir from comment #8)

Works fine, except for the flickers.

Does this configuration really flicker? This one has gfx.webrender.software=true. Please set it for the EGL test back to false, close Firefox, start MOZ_X11_EGL=1 firefox, set a bookmark, open the main menu, open the context menu and then attach about:support. (Desired outcome: It should show that "WebRender" is still used, has not fallen back to "Basic" or "WebRender (Software)" and has no graphics error log.)

Comment 10

[Mubashshir]

Attachment: offtopic: MOZ_X11_EGL

Comment 11

[Mubashshir]

mozregression --good 2021-02-01 --bad 92 --pref gfx.webrender.all:true
Output

2:01.51 ERROR: Build was expected to be good! The initial good/bad range seems incorrect.

Comment 12

[Darkspirit]

1. In worse case you are seeing the old bug 1518796 which haven't been able to reproduce anymore (I think).

   Can you check if

• this is bad? mozregression --launch 92 --pref gfx.webrender.all:true
• but this is good? MOZ_GTK_TITLEBAR_DECORATION=none mozregression --launch 92 --pref gfx.webrender.all:true

2. Please try going back further: mozregression --good 2020-02-01 --bad 92 --pref gfx.webrender.all:true

Comment 13

[Mubashshir]

(In reply to Darkspirit from comment #12)

1. In worse case you are seeing the old bug 1518796 which haven't been able to reproduce anymore (I think).

   Can you check if

• this is bad? mozregression --launch 92 --pref gfx.webrender.all:true
• but this is good? MOZ_GTK_TITLEBAR_DECORATION=none mozregression --launch 92 --pref gfx.webrender.all:true

I think it's not that one.

• mozregression --launch 92 --pref gfx.webrender.all:true is bad.
• mozregression --launch 92 --pref gfx.webrender.all:true is bad too.

2. Please try going back further: mozregression --good 2020-02-01 --bad 92 --pref gfx.webrender.all:true

Older builds(<80) crashed on launch, so I ran mozregression --bad 92 --pref gfx.webrender.all:true. it returned this pushlog url

Comment 14

[Darkspirit]

(In reply to Mubashshir from comment #13)

(In reply to Darkspirit from comment #12)

1. In worse case you are seeing the old bug 1518796 which haven't been able to reproduce anymore (I think).

   Can you check if

• this is bad? mozregression --launch 92 --pref gfx.webrender.all:true
• but this is good? MOZ_GTK_TITLEBAR_DECORATION=none mozregression --launch 92 --pref gfx.webrender.all:true

I think it's not that one.

• mozregression --launch 92 --pref gfx.webrender.all:true is bad.
• mozregression --launch 92 --pref gfx.webrender.all:true is bad too.

The second one must be started with MOZ_GTK_TITLEBAR_DECORATION=none environment variable. That env var really does not help?

Comment 15

[Mubashshir]

Attachment: env MOZ_GTK_TITLEBAR_DECORATION=none mozregression --launch 92 --pref gfx.webrender.all:true

(In reply to Darkspirit from comment #14)

(In reply to Mubashshir from comment #13)

(In reply to Darkspirit from comment #12)

1. In worse case you are seeing the old bug 1518796 which haven't been able to reproduce anymore (I think).

   Can you check if

• this is bad? mozregression --launch 92 --pref gfx.webrender.all:true
• but this is good? MOZ_GTK_TITLEBAR_DECORATION=none mozregression --launch 92 --pref gfx.webrender.all:true

I think it's not that one.

• mozregression --launch 92 --pref gfx.webrender.all:true is bad.
• mozregression --launch 92 --pref gfx.webrender.all:true is bad too.

The second one must be started with MOZ_GTK_TITLEBAR_DECORATION=none environment variable. That env var really does not help?

Nope.

Comment 16

[Darkspirit]

(In reply to Mubashshir from comment #13)

2. Please try going back further: mozregression --good 2020-02-01 --bad 92 --pref gfx.webrender.all:true

Older builds(<80) crashed on launch, so I ran mozregression --bad 92 --pref gfx.webrender.all:true. it returned this pushlog url

Likely because of the sandbox. Please try:
MOZ_DISABLE_CONTENT_SANDBOX=1 mozregression --good 2020-02-01 --bad 92 --pref gfx.webrender.all:true

If that doesn't work, you could go even further back, but it could become difficult as you could hit different bugs:
MOZ_DISABLE_CONTENT_SANDBOX=1 mozregression --good 2019-01-15 --bad 2020-02-01 --pref gfx.webrender.all:true

Comment 17

[Mubashshir]

(In reply to Darkspirit from comment #16)

(In reply to Mubashshir from comment #13)

2. Please try going back further: mozregression --good 2020-02-01 --bad 92 --pref gfx.webrender.all:true

Older builds(<80) crashed on launch, so I ran mozregression --bad 92 --pref gfx.webrender.all:true. it returned this pushlog url

Likely because of the sandbox. Please try:
MOZ_DISABLE_CONTENT_SANDBOX=1 mozregression --good 2020-02-01 --bad 92 --pref gfx.webrender.all:true

If that doesn't work, you could go even further back, but it could become difficult as you could hit different bugs:
MOZ_DISABLE_CONTENT_SANDBOX=1 mozregression --good 2019-01-15 --bad 2020-02-01 --pref gfx.webrender.all:true

https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ded7be1841d1a72d3456f34952719c7e1433d9b2&tochange=7ea6b52780c0a526eee4761be3ddbec9818cd441

Comment 18

[Darkspirit]

This range doesn't seem to make sense. The bug might not occur reliably. If a build is seemingly good, you could retry it by typing "r" instead of "g".

Comment 19

[Darkspirit]

(In reply to Mubashshir from comment #3)

My Setup:
DE: Xfce 4.16
WM: Xfwm4(w/o compositor)
Compositor: Picom vgit-ee7d9

Can't reproduce with Nvidia driver 470, Ubuntu 21.04 and xubuntu-desktop with compositing enabled and disabled.
Does it still occur if you disable Picom?
Would setting gfx.webrender.allow-partial-present-buffer-age=false and restarting Firefox help?

Comment 20

[Mubashshir]

Does it still occur if you disable Picom?

Yeah, it occurs even after stopping picom, the blocks becomes black instead of being transparent though

Would setting gfx.webrender.allow-partial-present-buffer-age=false and restarting Firefox help?

Didn't help.

Comment 21

[Darkspirit]

Does this bug still occur with latest Nightly?
mozregression --launch 2021-09-20 --pref gfx.webrender.all:true

Comment 22

[Mubashshir]

Attachment: Firefox nightly 2021-09-20

The bug is still present in nightly, although the amount reduced.

Comment 23

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

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

For more information, please visit auto_nag documentation.

Comment 24

[sgl4kn]

Can confirm, however for me this happens just for the following conditions:

• nVidia driver (RTX 3050) v511.65
• Multi-Monitor Setup
• Both Monitors have to be configured in clone mode (primary 144Hz, secondary 60Hz)
• HW accelearation has to be turned on in FF (standard setting)

However, seems there's no workaround currently. Tested different driver versions & setting (vSync / GSYNC). Furthermore FF settings like "layout.frame_rate" have no effect to minder the flickering.

Nevertheless, for me it does not happen if the monitors are in extended mode or if an AMD GPU is used.

Comment 25

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

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Comment 26

[Robert Mader [:rmader]]

Hi! Does the issue still happen for you or was it fixed somewhere in the meantime? Thanks!

Comment 27

[Mubashshir]

Sorry... I forgot about the bug... was probably fixed in or after v102, cause didn't notice the issue since last year...

Comment 28

[Robert Mader [:rmader]]

Great, thanks!