You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Linux version:Arch Linux
- Kernel Version: Linux arch 6.12.63-1-lts #1 SMP PREEMPT_DYNAMIC Thu, 18 Dec 2025 14:48:15 +0000 x86_64 GNU/Linux
- GPU Model: 06:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1636] (rev d1)
- Mesa/GPU Driver Version: 1:25.3.2-1
- Window Manager and Version: sway 1.11
- Source of mpv: Arch package
- Latest known working version: N/A
- Issue started after the following happened: Can also repro in previous versions (0.39 I think)
Reproduction Steps
mpv --no-config /dev/video0 /dev/video0
Press > or run playlist-next
Get segmentation fault.
Expected Behavior
No such crash.
Actual Behavior
Crash somewhere inside ffmpeg code (not familiar with the internals, wanted to track it here in case buffer misuse is inside mpv, can't repro via ffmpeg directly)
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.
Possibly related V4L2 shutdown crash on ARM64/Asahi
Historical diagnostics from September 21, 2026 may show another manifestation of the V4L2 packet-lifetime issue linked above. The immediate crash site differs, so I have not established that it is the same bug.
A webcam overlay crashed during controller-requested shutdown (SIGTERM) in three runs: twice with gpu-next/Asahi Vulkan, and once with gpu-next after adding --gpu-api=opengl. All three coredumps report SIGSEGV / SEGV_MAPERR. The OpenGL run logged:
VO: [gpu-next] 640x720 nv12
[ffmpeg/demuxer] video4linux2,v4l2: Some buffers are still owned by the caller on close.
Exiting... (Quit)
Historical launch command, with only the IPC socket pathname normalized:
Both backend paths continue through libplacebo's frame queue and pl_queue_update. Unnamed frames were unresolved in systemd's traces; stack location alone does not establish a libplacebo/Mesa defect.
Environment: Arch Linux ARM/Asahi, aarch64. Package history and the current matching versions show mpv 1:0.41.0-6, FFmpeg 2:9.0.1-4, libplacebo 7.360.1-6, mesa and vulkan-asahi 1:26.2.3-1. No intervening updates to those packages are recorded after the incident. mpv --version reports v0.41.0, libplacebo v7.360.1 and FFmpeg n9.0.1.
Changing the overlay renderer to --vo=gpu --gpu-api=opengl avoided new coredumps in two subsequent recording/stop cycles, including a 17.856-second recording that decoded successfully. This is a limited workaround observation, not a demonstrated root-cause fix.
These are recovered historical diagnostics, not a fresh latest/master reproduction. A full --gpu-debug crash log and fully symbolized backtrace are unavailable in the recovered evidence. I am adding the ARM/Asahi, shutdown and cross-backend observations as possibly related evidence for the existing FFmpeg investigation, not asserting a confirmed duplicate or requesting a separate GPU-driver bug.
The root cause is already documented and reported upstream, see my comment above. No need to reiterate it again. Feel free to propose fixes upstream for this issue.
Activity
kasper93 commentedon Aug 9, 2026
For reference: https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/21358, https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/21621
Not a mpv bug, need upstream fix to not orphan AVPackets.
jeffscottward commentedon Sep 22, 2026
Possibly related V4L2 shutdown crash on ARM64/Asahi
Historical diagnostics from September 21, 2026 may show another manifestation of the V4L2 packet-lifetime issue linked above. The immediate crash site differs, so I have not established that it is the same bug.
A webcam overlay crashed during controller-requested shutdown (SIGTERM) in three runs: twice with gpu-next/Asahi Vulkan, and once with gpu-next after adding --gpu-api=opengl. All three coredumps report SIGSEGV / SEGV_MAPERR. The OpenGL run logged:
Historical launch command, with only the IPC socket pathname normalized:
For the OpenGL comparison, --gpu-api=opengl was added. No --no-config reproduction was performed.
Both Vulkan stacks start with:
The OpenGL stack starts with:
Both backend paths continue through libplacebo's frame queue and pl_queue_update. Unnamed frames were unresolved in systemd's traces; stack location alone does not establish a libplacebo/Mesa defect.
Environment: Arch Linux ARM/Asahi, aarch64. Package history and the current matching versions show mpv 1:0.41.0-6, FFmpeg 2:9.0.1-4, libplacebo 7.360.1-6, mesa and vulkan-asahi 1:26.2.3-1. No intervening updates to those packages are recorded after the incident. mpv --version reports v0.41.0, libplacebo v7.360.1 and FFmpeg n9.0.1.
Changing the overlay renderer to --vo=gpu --gpu-api=opengl avoided new coredumps in two subsequent recording/stop cycles, including a 17.856-second recording that decoded successfully. This is a limited workaround observation, not a demonstrated root-cause fix.
These are recovered historical diagnostics, not a fresh latest/master reproduction. A full --gpu-debug crash log and fully symbolized backtrace are unavailable in the recovered evidence. I am adding the ARM/Asahi, shutdown and cross-backend observations as possibly related evidence for the existing FFmpeg investigation, not asserting a confirmed duplicate or requesting a separate GPU-driver bug.
Filed by GPT-6 Astra via Oh My Pi.
kasper93 commentedon Sep 22, 2026
The root cause is already documented and reported upstream, see my comment above. No need to reiterate it again. Feel free to propose fixes upstream for this issue.