Stuck pixels/artifacts at screen edge when using display scaling

[Roger-Roger-debug]

Hyprland version

0.48.1

Regression

Before commit 6967a31 this issue didn't happen.

Describe the bug

I've got two displays with a resolution of 3440x1440 and 2560x1440 and both have a scaling of 1.33333. The color of my window borders will "stick" to the last row and column of pixels. This used to happen with the cursor as well, but I can no longer reliably reproduce that after updating from 0.46.2 to 0.48.1.

Changing the display scaling down to 1 and then back to 1.33333 while hyprland is running fixes the issue.

I tried recording my screen but it doesn't show up with wf-recorder.

Something that might be related is that games report the screen resolution as 3439x1439, I guess that's the same row and column missing that doesn't get repainted in normal desktop usage.

Reproduction steps

1. Have a monitor with a high resolution
2. Set the scaling to 1.33333
3. Have the border color/shadow touch the screen edge

System info and config

info.txt

[UnnaturalTwilight]

I have the same issue on Hyprland 0.52.2
My screen is 2256x1504 (Framework laptop) at 1.175 scale
It is most visible if I set background_color = rgb(00FFFF) in my config. If I then reload hyprpaper the background dose not quite reach the edge of the screen.

[tekstryder]

I've got two displays with a resolution of 3440x1440 and 2560x1440 and both have a scaling of 1.33333. The color of my window borders will "stick" to the last row and column of pixels

Replying to the OP. Yes, this was one of the first issues I noticed when I first moved to Hyprland.

Display (PHL 328E1): 3840x2160 @ 1.33x in 32"
Display (DELL U2711): 1440x2560 @ 1.07x in 27"

So I worked around it with a 1px offset (2881 vs 2880) on secondary display:

monitor = DP-1, 3840x2160, 0x0, 1.333333
monitor = DVI-D-1, 2560x1440, 2881x-425, 1.066667, transform, 3

But, this no longer occurs on latest git, and I reverted to 2880 without the issue of "stuck" pixels occurring.

I didn't bisect to the commit that fixed it, or even remember a ballpark time frame.