Borked Damage Tracking of Popup Menus on Chromium 136

[Sewer56]

Hyprland version

Hyprland 0.48.1 built from branch at commit 29e2e59 (version: bump to v0.48.1).

Also tested on git (1ce614d), no difference.

Regression

Not to my awareness.

Describe the bug

On Chromium 136 (136.0.7103.59), damage tracking of popups appears to be currently broken:

2025-05-06.03-21-15.mp4

2025-05-06.03-09-24.mp4

It's on Nvidia :( [I wish AMD released a higher end GPU this gen]. I do have an AMD iGPU, but I haven't checked if it happens there yet.
(I haven't looked at the code, so I'm not sure if damage tracking code has any hardware dependencies).

Only Chromium 136. Chromium 135 and below does not reproduce this behaviour.

Reproduction steps

I installed pacman package extra/chromium with version 136.0.7103.59-1.1.
Afterwards the issue appeared.

The issue was not present in previous package versions, e.g. 135.0.7049.114.

System info and config

info.txt

[Zebra2711]

Pls open chrome://gpu/ and share the about-gpu-XXXXXX.txt report file. It might be a Wayland hardware acceleration issue. I recommend running chromium and electron apps on x11 because wayland is not fully supported yet and has many bugs; also, hardware acceleration is not fully supported on wayland

[Sewer56]

about-gpu-2025-05-06T03-58-43-342Z.txt

No worries, here it is.

---

X11 is a no-go for me, due to fractional scaling. I'd rather have buggy popups than blurry text.

[Zebra2711]

I was able to reproduce that issue on wayland before, which is why I now run it on x11, and I don't have any blurry text issues. You can add or remove some flags using the information here: https://peter.sh/experiments/chromium-command-line-switches, hope this helps

[RichAyotte]

I'm seeing this on my AMD Radeon RX 6700 XT as well.

about-gpu-2025-05-06T12-40-09-727Z.txt

https://youtu.be/sWAaBi3mOLU

ref: #10046 (comment)

Hyprland 0.48.0 built from branch main at commit adbae0f74d951e06c575bad3c81a944027dfe413  (protocols: refactor class member vars (a-m) (10265)).
Date: Sat May 3 18:13:29 2025
Tag: v0.48.0-150-gadbae0f7, commits: 6072
built against:
 aquamarine 0.8.0
 hyprlang 0.6.1
 hyprutils 0.7.0
 hyprcursor 0.1.12
 hyprgraphics 0.1.3

no flags were set

[tannerellen]

Yep, can confirm this is happening for me on latest git on my all AMD system.

[vaxerski]

#10305

[RichAyotte]

Confirming that #10306 fixed the issue.