hardware acceleration bug with some videos

mpv Information

mpv v0.41.0 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Feb 11 2026 22:07:06
libplacebo version: v7.360.1
FFmpeg version: n8.0.1 (runtime n8.1.1)
FFmpeg library versions:
   libavcodec      62.11.100 (runtime 62.28.101)
   libavdevice     62.1.100 (runtime 62.3.101)
   libavfilter     11.4.100 (runtime 11.14.101)
   libavformat     62.3.100 (runtime 62.12.101)
   libavutil       60.8.100 (runtime 60.26.101)
   libswresample   6.1.100 (runtime 6.3.101)
   libswscale      9.1.100 (runtime 9.5.101)

Other Information

- Linux version:Arch Linux

- Kernel Version:Linux laptop 7.0.10-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 23 May 2026 14:21:20 +0000 x86_64 GNU/Linux

- GPU Model:04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c1)

- Mesa/GPU Driver Version:26.1.1-arch1.2
- Window Manager and Version:KDE 
- Source of mpv: archlinux repo
- Latest known working version: 0.40.0

Reproduction Steps

play a video file that has this issue with command:
mpv --no-config --hwdec=yes video.mkv

Expected Behavior

video should play fine

Actual Behavior

video has visual artifact as shown in picture
(which is the same pattern for all the videos that have this issue)

Log File

output2.txt

Sample Files

test.zip

I carefully read all instruction and confirm that I did the following:

• I tested and confirmed that the issue exists with the latest release version or newer.
• I provided all required information including system and mpv version.
• I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of --log-file=output.txt.
• I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
• I attached the full, untruncated log file.
• I attached the backtrace in the case of a crash.

Reproduce the artifact with mpv 0.41.0 using mpv --no-config --hwdec=yes video.mkv and the attached test.zip, then compare with the reported working 0.40.0 behavior. Read output2.txt alongside the reproduction details and use the attached image to identify the failure pattern; done means the sample videos play without visual artifacts under hardware acceleration.