Open Bug 1657905 Opened 4 years ago Updated 2 years ago

Firefox is laggy when using on external 75Hz 1080p monitor, on Pop OS, with and without webrenderer on, but window works perfectly fine when moved over to the laptop's display.

Categories

(Core :: Graphics, defect, P3)

79 Branch
Desktop
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: arjun.s.singh, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: perf)

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36

Steps to reproduce:

Connect external monitor to laptop via HDMI. Monitor specifications: 1080p, 75Hz.
Laptop specifications: i5 5200U, GTX 830M, 1366x768 display.
OS: Pop OS 20.04. This occurs when display is in "Join displays", i.e., extended mode, as well as single display mode.

Actual results:

Scrolling and web browsing in general is very choppy on external monitor, both with and without webrenderer on. It is more noticeably choppy with webrenderer on.

Expected results:

Smooth scrolling and web browsing is expected on the external monitor. When running on Windows 10 on the same system, this issue is not observed. This occurs on Pop OS, Linux, though. Moreover, chromium based browsers do not face this issue, even on Pop OS, so it is definitely an issue with firefox.

Please open about:support, click on "Copy text to clipboard" and paste it here. Thanks!
I assume Firefox renders at 60 Hz no matter what your monitor uses.

Blocks: vsync
Component: Untriaged → Graphics
Keywords: perf
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → Desktop
See Also: → 1647166, 1630490

(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #1)

Please open about:support, click on "Copy text to clipboard" and paste it here. Thanks!
I assume Firefox renders at 60 Hz no matter what your monitor uses.

Hello. Thanks for taking your time in assisting me with this.
I don't know if firefox runs at 60Hz no matter what, because there is an option called layout.frame_rate, right? Plus, I've seen some animations run at a faster frame rate, in those cases. Well, I don't know if it's placebo or what, but what I can be sure is that I definitely face some sort of problem on firefox on Linux, and I don't face this choppiness on Windows 10, or on Chromium browsers on Linux.
I tried both the .deb and the flatpak versions of firefox, to see if that made a difference, but it didn't.

Assuming the external monitor is connected to the GTX 830M GPU, this is a Xorg issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1028

(In reply to Michel Dänzer from comment #4)

Assuming the external monitor is connected to the GTX 830M GPU, this is a Xorg issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1028

I don't know the technicalities of how any of this works, but doesn't that mean that the entire display should be laggy? Which it isn't. System wide animations, and other applications run run at 75Hz.

Update:
Setting the monitor's refresh rate to 60Hz removes the choppiness.
Moreover, disabling laptop display and enabling webrenderer on + setting layout.frame_rate to 75 makes firefox run as expected.
But both defeat the purpose of an external 75Hz monitor..

Severity: -- → S3
Priority: -- → P3

(In reply to Darkspirit from comment #10)
From the terminal, I launched FF without any error output in terminal using this command:
pranav@exam ~> firefox MOZ_ENABLE_WAYLAND=1

But, in X11, it throwed this error:
pranav@exam ~> firefox MOZ_X11_EGL=1
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
.........

Also tried Wrote "MOZ_X11_EGL=1" inside .profile file, but it didn't make any difference. FF is still laggy and unresponsive until I hit "Super".
Neither of the methods I used are responsive. Do I need to use Chromium for a while until FF 83 is released as stable because looking at current state its complety unusable?! Or use FF after Ubuntu non-LTS 20.10 is released in 22 October with new stable GNOME.

Flags: needinfo?(jmathies)

(In reply to Pranav bhattarai from comment #11)
Your quoted terminal commands are super strange, usually you need to write env vars bevor the command.
You might have been using MOZ_ENABLE_WAYLAND=1, which is so experimental that it's not even enabled in Firefox' alpha version (Nightly) yet: bug 1543600. Try to remove all MOZ_ env vars. If it's bug 1653850, the bug would only occur with MOZ_ENABLE_WAYLAND=1. Please don't comment in this bug because it doesn't seem like you have the same problem. Please report your own bug and don't needinfo random people: https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A+WebRender
Please also open about:support, click on "Copy text to clipboard" and paste it into the attachment field. Thanks

Flags: needinfo?(jmathies)

I have added a comment which may be relevant to this issue at bug 1647166 comment 3 where I describe a consistent workaround and share my system information. Those interested in resolving this issue, please follow my link. I apologize if my comment is misplaced. I figured that issue ticket was the ideal place.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: