mpv-player / mpv-player/mpv

mpv closes on the last frame, instead of letting it be seen

Open
#16,942 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

os:linux
Dominant language
C
Stars
37k
Forks
3.5k
Avg merge
1d 10h
Merged PRs (30d)
22

Description

mpv Information
mpv v0.40.0-dirty Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
libplacebo version: v7.349.0 (v7.349.0)
FFmpeg version: n8.0
FFmpeg library versions:
   libavcodec      62.11.100
   libavdevice     62.1.100
   libavfilter     11.4.100
   libavformat     62.3.100
   libavutil       60.8.100
   libswresample   6.1.100
   libswscale      9.1.100
Other Information
- Linux version: Arch Linux
- Kernel Version: 6.17.3-arch2-1
- GPU Model: Graphics Processor 1: Intel® Iris® Xe Graphics - Graphics Processor 2: NVIDIA GeForce GTX 1650
- Mesa/GPU Driver Version: mesa-1:25.2.5-3
- Window Manager and Version: KDE Plasma Version: 6.4.5
- Source of mpv: Flatpak
- Latest known working version: 
- Issue started after the following happened:
Reproduction Steps

1- Have a video with a very noticeable last frame.
2- Skip to the ending, then use [>.] key to navigate frame-by-frame to see that frame.

Expected Behavior

Being able to see that frame.
Even better if pressing forwards frame-by-frame with the [>.] key to go one a frame beyond the last frame wouldn't close MPV.

Actual Behavior

If you reach the last frame of a video by going frame-by-frame with the [>.] key, MVP will close as if you were watching the video.

It affects other players:
https://bugs.kde.org/show_bug.cgi?id=497841#c7

Log File

output.txt

Sample Files

No response

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the behavior described in the frame-by-frame steps using the attached output.txt log as a reference. Inspect mpv's frame-stepping and end-of-file handling, then verify that reaching the last frame leaves it visible and does not close the player.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.