-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Open
Labels
Description
mpv Information
There is a problem when playing long streams(more than an hour is perfect for testing) and skipping to a different position. Up to build #15515 it was working perfectly, but after that it’s just broken. Short files work very well and local files too because the problem is only skipping long streams, which causes a crash here.
I tracked down the issue and this here is the last working vesion and every version after that is affected:
https://github.com/mpv-player/mpv/actions/runs/21776692541Other Information
- Windows version: Windows 11 (Version 10.0.26100.6899)
- GPU model, driver and version: AMD 7900 XTX
- Source of mpv: https://github.com/mpv-player
- Latest known working version: https://github.com/mpv-player/mpv/actions/runs/21776692541
Reproduction Steps
To reproduce the problem, just try playing a long audio stream and skip 1 or 2 minutes. The player will never play the stream again and from that moment on, it is broken. Trying to play another stream or even a local file will crash the mpv player immediately.
Expected Behavior
To skip to the desired position and resume like this version and all previous one do:
https://github.com/mpv-player/mpv/actions/runs/21776692541
Actual Behavior
The latest version does not resume and crash when trying to play another one.
Log File
Sample Files
I don't have one but a long stream should do the trick.
I carefully read all instruction and confirm that I did the following:
- I tested with the latest mpv version to validate that the issue is not already fixed.
- 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.
Reactions are currently unavailable