Closed Bug 1705695 Opened 3 years ago Closed 2 years ago

[LINUX] Rendering at 60Hz despite the monitor refresh rate set to 144Hz when using MOZ_X11_EGL=1 (layout.frame_rate fixes it)

Categories

(Core :: Graphics, defect)

Firefox 87
defect

Tracking

()

RESOLVED DUPLICATE of bug 1640779

People

(Reporter: aros, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:87.0) Gecko/20100101 Firefox/87.0

Steps to reproduce:

I have a monitor which has a 144Hz refresh rate which is confirmed by xrandr/glxgears output in Linux/Fedora 33 with proprietary NVIDIA drivers 465.24.02 under X.org/XFCE (no compositing).

However both www.testufo.com/refreshrate and www.vsynctester.com report 60Hz.

I've found a workaround which is to set layout.frame_rate to 144 but I hate to do it manually because most users never touch about:config and this is not required under Windows.

Setting layers.acceleration.force-enabled to true and gfx.webrender.all to true makes no difference.

I'm using the official Firefox build, version 87 ( https://ftp.mozilla.org/pub/firefox/releases/87.0/linux-x86_64/ )

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.

Component: Untriaged → Graphics: WebRender
Product: Firefox → Core
Blocks: vsync
Severity: -- → S3
Priority: -- → P3
Component: Graphics: WebRender → Graphics

The component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit auto_nag documentation.

Priority: P3 → --

New findings:

When using MOZ_X11_EGL=1 Firefox defaults to 60Hz.

When not using this, Firefox defaults to the actual monitor refresh rate.

Summary: [LINUX] Rendering at 60Hz despite the monitor refresh rate set to 144Hz → [LINUX] Rendering at 60Hz despite the monitor refresh rate set to 144Hz when using MOZ_X11_EGL=1 (layout.frame_rate fixes it)

Bug 1720634 could be related, I've no idea.

This should have been fixed by bug 1640779 in FF 95 - please reopen if that's not the case.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.