Grouping multiple firefox windows results in lag / stutter when scrolling

[talyz]

Already reported ? *

• I have searched the existing open and closed issues.

Regression?

I don't know, I started using Hyprland only recently

System Info and Hyprland Version

System/Version info

Hyprland 0.47.0 built from branch v0.47.2-b at commit 882f7ad7d2bbfc7440d0ccaef93b1cdd78e8e3ff  (version: bump to 0.47.2).
Date: 2025-02-02
Tag: v0.47.2, commits: 882f7ad7d2bbfc7440d0ccaef93b1cdd78e8e3ff
built against:
 aquamarine 0.7.2
 hyprlang 0.6.0
 hyprutils 0.5.0
 hyprcursor 0.1.11
 hyprgraphics 0.1.1


no flags were set


System Information:
System name: Linux
Node name: sythe
Release: 6.13.1
Version: #1-NixOS SMP PREEMPT_DYNAMIC Sat Feb  1 16:21:26 UTC 2025


GPU information: 
c3:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev dd) (prog-if 00 [VGA controller])


os-release: ANSI_COLOR="0;38;2;126;186;228"
BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
BUILD_ID="25.05.19700101.dirty"
CPE_NAME="cpe:/o:nixos:nixos:25.05"
DEFAULT_HOSTNAME=nixos
DOCUMENTATION_URL="https://nixos.org/learn.html"
HOME_URL="https://nixos.org/"
ID=nixos
ID_LIKE=""
IMAGE_ID=""
IMAGE_VERSION=""
LOGO="nix-snowflake"
NAME=NixOS
PRETTY_NAME="NixOS 25.05 (Warbler)"
SUPPORT_URL="https://nixos.org/community.html"
VARIANT=""
VARIANT_ID=""
VENDOR_NAME=NixOS
VENDOR_URL="https://nixos.org/"
VERSION="25.05 (Warbler)"
VERSION_CODENAME=warbler
VERSION_ID="25.05"


plugins:

Description

I recently tried to move away from using hy3, replacing its tabs with native groups and found that all of a sudden firefox got really laggy and stuttery when scrolling. This is particularly noticeable on my external 144Hz monitor.

Scrolling is really smooth when using hy3 or not grouping the windows, but gets progressively worse when adding more windows to a native group. I usually have around 5 firefox windows grouped and using the whole workspace area. If I group 4 of them and put them on a different workspace, keeping one single window on a different workspace, the single window is smooth as long as the other workspace is hidden. If it's put on a secondary monitor, the single window starts lagging, though.

Any non-firefox windows do not seem to be affected the same way. Chromium, if grouped in with the firefox windows, still has really smooth scrolling.

How to reproduce

1. Connect a high refresh rate, high resolution display
2. Group a few firefox windows together on a workspace on the display
3. Scroll

Attach not paste

• I understand that all text files must be attached, and not pasted directly. If not respected, this issue will likely get closed as spam

Checklist of files to include below

• Hyprland config - hyprctl systeminfo -c (always include)
• Crash report (always include in case of crash)
• Video (always include in case of a visual bug)
• Logs (might contain useful info such as errors)

Additional info & File uploads

config.txt
firefox-hyprland-stutter.mp4

[nnyyxxxx]

can you try #9354

[talyz]

Yes, probably should have mentioned that I already did; both by applying to 0.47.2 and running on main. Unfortunately, it didn't make any difference.

[nnyyxxxx]

oh okay

[nnyyxxxx]

fps does seem to get lower when multiple firefox windows are grouped compared to just having one instance ( one instance meaning: not grouped ) open, haven't tried with #9354 yet though only on main

[nnyyxxxx]

actually it's probably because it's grouped not because their are multiple instances of it grouped

e.g.

one firefox window grouped
notice reduced fps

compared to

a lot of firefox windows grouped
notice reduced fps

[nnyyxxxx]

that would explain why #9354 doesn't fix the issue

[talyz]

Well, to me it gets worse if multiple windows are added to the group. I've attached a video to the description that shows the difference I see. It's worse in real life, but I think it should be visible enough.

[talyz]

Hm, so after upgrading to firefox 135 and refreshing my state, I can no longer reproduce this. No idea what caused it, but maybe just a bug in firefox? Guess it's not worth keeping this open, regardless.