Going fullscreen then seeking causes strange ghosting artifacts

[McBaws]

mpv Information

mpv v0.38.0-741-ga0ebfc34 Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
 built on Sep  4 2024 00:07:54
libplacebo version: v7.349.0 (v7.349.0-9-gefb8934-dirty)
FFmpeg version: N-116848-g3f9b78bd1
FFmpeg library versions:
   libavcodec      61.11.100
   libavdevice     61.2.100
   libavfilter     10.2.102
   libavformat     61.5.101
   libavutil       59.35.100
   libswresample   5.2.100
   libswscale      8.2.100

Other Information

- Windows version: Microsoft Windows [Version 10.0.22631.4169]
- GPU model, driver and version: RTX 3050 Laptop 4GB, Geforce Game Ready Driver 561.09, 32GB System RAM
- Source of mpv: Replicated on various builds, including shinchiro git-ef19a4a
- Introduced in version: Unsure, error occurs in v0.38.0 and git latest

Reproduction Steps

Start mpv with --no-config and --profile=high-quality, press fullscreen, and seek. Strange ghosting occurs.

This ghosting also occurs when OSD text appears (such as text showing the subtitle track has changed), and a ghost image of subtitles appears if their visibility is toggled. The ghosting happens almost every time the program goes fullscreen, but can also appear randomly after seeking or framestepping after already being fullscreen for a while.

The error doesn't occur when not fullscreen. My display resolution is 3072x1920.

My laptop has integrated AMD graphics and a dedicated GPU. If I run my desktop and mpv on integrated graphics, the error doesn't occur. If I run my desktop on integrated graphics and mpv on dedicated GPU, the error doesn't occur. It only occurs if I run everything on the dedicated GPU.

Expected Behavior

Normal looking image

Actual Behavior

Strange ghosting artifacts

Log File

Single backwards framestep exhibited the issue: output 1.txt

Toggling subtitle visibility and seeking exhibited the issue: output 2.txt

Subtitle visibility with vulkan: output vk.txt

Sample Files

Occurs on any video file.

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

• [X] I tested with the latest mpv version to validate that the issue is not already fixed.
• [X] I provided all required information including system and mpv version.
• [X] 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.
• [X] I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
• [X] I attached the full, untruncated log file.
• [X] I attached the backtrace in the case of a crash.