Closed Bug 1928167 Opened 18 days ago Closed 15 days ago

Flickers and glitches on Linux and NVIDIA

Categories

(Core :: Graphics, defect, P2)

Firefox 132
defect

Tracking

()

RESOLVED DUPLICATE of bug 1924578

People

(Reporter: aliakbarmostafaei, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(4 files)

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

Steps to reproduce:

Setup info:
OS: Ubuntu 24.04.1
GPU: NVIDIA 1030 on Xorg
Drivers: v550.120
Firefox 132

  1. Visit tradingview.com or binance.com
  2. Have the tab open for a while
  3. Interact with charts on the page

Actual results:

Flickers show up on the charts

Expected results:

Charts should display correctly during interactions

Attachment #9434314 - Attachment description: Screencast from 2024-10-30 12-55-35.webm → Screencast from binance.com

I have also tried a new profile without any settings change and addons installed and the issue persists. I also don't remember this issue on 12x.x releases, this seems like a regression.

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

Component: Untriaged → Graphics
Product: Firefox → Core

This isn't exactly the URL used in the binance repro case, but it's a similar one that works in the USA: https://www.binance.us/spot-trade/ethusdt.

We'll find someone who can reproduce.

Blocks: gfx-triage
Severity: -- → S2
Priority: -- → P2

(In reply to Brad Werth [:bradwerth] from comment #4)

This isn't exactly the URL used in the binance repro case, but it's a similar one that works in the USA: https://www.binance.us/spot-trade/ethusdt.

We'll find someone who can reproduce.

I was able to reproduce it with the url provided, the odd thing is the issue only exhibits if the window/tab is left open for a while and then even tab reloads won't fix it only closing the window and re-opening a new one remedies the effect and the cycle repeats!

I narrowed down the offending release to 128, previous releases did not exhibit this issue. I'm trying to mozregression right now, to see if I can narrow it down further.

See Also: → 1907828

Ali, can you please set the widget.dmabuf.enabled pref in about:config to false and see if that causes the behavior to go away?

Flags: needinfo?(aliakbarmostafaei)
See Also: → 1924578

(In reply to Bob Hood [:bhood] from comment #9)

Ali, can you please set the widget.dmabuf.enabled pref in about:config to false and see if that causes the behavior to go away?

Setting widget.dmabuf.enabled to false indeed resolved the issue, another fix I found was installing the nvidia-vaapi-driver and setting the widget.dmabuf.force-enabled to true.

Flags: needinfo?(aliakbarmostafaei)

(In reply to Ali Akbar from comment #10)

(In reply to Bob Hood [:bhood] from comment #9)

Ali, can you please set the widget.dmabuf.enabled pref in about:config to false and see if that causes the behavior to go away?

Setting widget.dmabuf.enabled to false indeed resolved the issue, another fix I found was installing the nvidia-vaapi-driver and setting the widget.dmabuf.force-enabled to true.

Correction: Having the widget.dmabuf.force-enabled set to true with the vaapi-driver makes the flickers a lot less but does not completely fix the issue as the first solution did.

Duplicate of this bug: 1928388
Status: UNCONFIRMED → RESOLVED
Closed: 15 days ago
Duplicate of bug: 1924578
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: