mpv crashed with SIGSEGV in _dl_close()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mpv (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This happens with the default options with nvidia hardware on wayland.
```bash
$ mpv file.mp4
(+) Video --vid=1 (*) (h264 1280x720 25.001fps)
(+) Audio --aid=1 --alang=fra (*) (aac 2ch 48000Hz)
[vo/gpu/wayland] GNOME's wayland compositor lacks support for the idle inhibit protocol. This means the screen can blank during playback.
[1] 17762 segmentation fault (core dumped) mpv
```
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: mpv 0.34.1-1ubuntu3
ProcVersionSign
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckR
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 10 16:56:40 2022
ExecutablePath: /usr/bin/mpv
InstallationDate: Installed on 2022-04-07 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcCmdline: mpv --player-
SegvAnalysis:
Segfault happened at: 0x7f8d44e5724d <_dl_close+29>: cmpb $0x0,0x31f(%rbx)
PC (0x7f8d44e5724d) ok
source "$0x0" ok
destination "0x31f(%rbx)" (0x0000031f) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: mpv
StacktraceTop:
_dl_close (_map=0x0) at ./elf/dl-
__GI__
__GI__
_dlerror_run (operate=<optimized out>, args=<optimized out>) at ./dlfcn/
__dlclose (handle=<optimized out>) at ./dlfcn/
Title: mpv crashed with SIGSEGV in _dl_close()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
separator:
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1967650, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.