Resizing the mpv window fast causes the system to stutter

[AhmedHalim96]

mpv Information

mpv v0.40.0 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
libplacebo version: v7.349.0
FFmpeg version: 7.1.1
FFmpeg library versions:
   libavcodec      61.19.101
   libavdevice     61.3.100
   libavfilter     10.4.100
   libavformat     61.7.100
   libavutil       59.39.100
   libswresample   5.3.100
   libswscale      8.3.100

Other Information

- Linux version:Fedora Linux 42 (Adams)
- Kernel Version: Linux fedora 6.14.9-300.fc42.x86_64
- GPU Model: Nvidia 3050 Mobile
- Mesa/GPU Driver Version: 575.57.08 and Mesa 25.0.7
- Window Manager and Version: AwesomeWM v4.3
- Source of mpv: The fedora repos
- Latest known working version: Not sure. probably version 39 or whatever was on fedora 41 as I noticed the issue after fedora 42 upgrade
- Issue started after the following happened: I upgraded to fedora 42. which upgraded mpv from 39 to version 40

Reproduction Steps

1. Run mpv --no-config ./lab.mp4
2. resizing the window using the mouse or keyboard somewhat fast.

Expected Behavior

it resizes without an issue

Actual Behavior

The whole system freezes for a second then continue

Log File

output.txt

also might be helpful running journalctl -f throws these warnings when the stutter happen

fedora kernel: NVRM: kdispApplyWarForBug3385499_v03_00: timeout waiting for METHOD_EXEC to IDLE
fedora kernel: NVRM: kdispApplyWarForBug3385499_v03_00: timeout waiting for channel state to UNCONNECTED

Sample Files

https://github.com/user-attachments/assets/e1a468c0-e27e-4bed-8e21-6849fd1d91b7

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.