SIGSEGV on vulkan fullscreen swapchain recreation (wayland-native, NVIDIA 595.91.07, mpv 0.41.0) — deterministic

Open
#18,577 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
40/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c, linux

Research direction

Start from the log line '(Re)creating swapchain' and locate where mpv (or libplacebo 7.360.0, which drives Vulkan swapchain setup for vo=gpu-next) triggers swapchain recreation on a wayland-native resize, likely under player/video or the gpu-next rendering path. Compare the fullscreen toggle path with the maximize path to see what differs in the resize size passed to the Vulkan surface. Done looks like either a minimal mpv-side guard that avoids the crash path on wayland-native fullscreen recreation, or a documented, reproducible confirmation that the fault is inside the NVIDIA driver with attachable logs and torture scripts.

Written by the indexing model from the issue text.

Description

priority:ignored-issue-template

Summary

On wayland-native with --gpu-api=vulkan, ANY fullscreen swapchain recreation to panel-native size segfaults deterministically — every time, both vo=gpu and vo=gpu-next, driver 595.91.07 (also 595.84). The last log line before the crash is always (Re)creating swapchain of size 2560x1440.

This is a sharper repro of the behavior previously seen as a cross-monitor maximize crash: the trigger is any fullscreen swapchain recreation on native wayland; cross-monitor move+maximize was merely one route into it. Xwayland (X11 context) is fully immune (20 maximize + 5 fullscreen cycles clean).

Minimal repro

# any h264 clip; toggle fullscreen a few times on a wayland-native display
mpv --no-config --vo=gpu-next --gpu-api=vulkan --msg-level=gpu=v clip.mp4
# press f (or maximize) once or twice → SIGSEGV

Our measured runs: fullscreen-only torture → SIGSEGV on cycle 1, 3/3. maximize-only → 20/20 clean. Xwayland → all clean.

Environment

  • mpv 0.41.0, libplacebo 7.360.0
  • NVIDIA RTX 3070, driver 595.91.07 (and 595.84 — same crash)
  • Ubuntu, GNOME/mutter wayland session, native (not XWayland) window

Full verbose logs + the torture scripts: happy to attach (they're in our repo's lane evidence dir). This looks like the NVIDIA vulkan driver's wayland swapchain recreation path; an mpv-side guard (refuse/recreate differently) may also be possible.

Dominant language
C
Stars
38.2k
Forks
3.7k
Avg merge
1d 13h
Merged PRs (30d)
76

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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.

More from mpv-player/mpv

All issues in mpv-player/mpv

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.