Open Bug 1630490 Opened 4 years ago Updated 3 years ago

Vsync cap on 144 hz Multi-monitor Setup & SW VSYNC

Categories

(Core :: Graphics, defect, P3)

76 Branch
Desktop
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: milakam, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux; rv:74.0) Gecko/20100101 Firefox/74.0

Steps to reproduce:

  1. Use a primary monitor with 144Hz (Freesync enabled) & a secondary monitor with 60Hz (an audio Hifi receiver in my case)
  2. Clone the desktop
  3. Start FF on the primary monitor and open testufo.com

Actual results:

Framerate is locked at 60Hz. Trying to enforce it via layout.frame_rate=144 crashes FF on Windows. If included in the pref.js it takes the setting, but is still just using 60Hz on testufo (or on the internal gfx.webrender.debug.profiler = true).

Expected results:

  1. FF should use the maximum framerate of connected monitors
  2. If that's not possible it should use the framerate of the monitor that it's currently displayed on

In any case FF shouldn't fallback to SW VSYNC if Freesync / Gsync is used ( https://bugzilla.mozilla.org/show_bug.cgi?id=1160216#c5 ).

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Graphics
Product: Firefox → Core
Blocks: wr-linux
OS: Unspecified → Linux
Priority: -- → P3
Hardware: Unspecified → Desktop
Blocks: vsync
See Also: → 1647166
See Also: → 1657905

Changing dependencies: vsync gets enabled together with Webrender, so this is blocked by, not blocking WR - if I understood the issue correctly. As bug 1627057 indirectly blocks bug 1491303 this creates a loop, thus moving to "see also"

No longer blocks: wr-linux
See Also: → wr-linux
You need to log in before you can comment on or make changes to this bug.