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

Aperta
#18,577 2 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
40/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c, linux

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
C
Stelle
38.2k
Fork
3.7k
Merge medio
1g 13h
PR unite (30g)
76

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di mpv-player/mpv

Tutte le issue di mpv-player/mpv

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.