vlc crashed with SIGSEGV when exitting from playing a wmv video

Bug #1475838 reported by RJVB
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vlc (Ubuntu)
New
Undecided
Unassigned

Bug Description

Nohting happens for a while, and then VLC crashes. KDE's Dragon Player (which uses libVLC) crashes too.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: vlc-nox 2.1.6-0ubuntu14.04.1 [modified: usr/lib/vlc/plugins/plugins.dat]
Uname: Linux 3.14.46-ck1-mainline-amdf10-rjvb x86_64
NonfreeKernelModules: ufsd zfs zunicode zcommon znvpair zavl
ApportVersion: 2.14.2-0ubuntu3
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Jul 18 09:27:50 2015
ExecutablePath: /usr/bin/vlc
InstallationDate: Installed on 2014-05-03 (440 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
ProcCmdline: /usr/bin/vlc --started-from-file /Volumes/Debian/Users/username/Ewin-Bola/JLeza/HumansAsAquifersVID.wmv
SegvAnalysis:
 Segfault happened at: 0x7f918305149a: mov 0x398(%rbx),%r13
 PC (0x7f918305149a) ok
 source "0x398(%rbx)" (0x00000397) not located in a known VMA region (needed readable region)!
 destination "%r13" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: vlc
StacktraceTop:
 ?? () from /usr/lib/libvlccore.so.7
 ?? () from /usr/lib/libvlccore.so.7
 start_thread (arg=0x7f91581bb700) at pthread_create.c:312
 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
Title: vlc crashed with SIGSEGV in start_thread()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip disk floppy fuse lpadmin plugdev sambashare sudo video

Revision history for this message
RJVB (rjvbertin) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1305106, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
RJVB (rjvbertin) wrote :

That bug doesn't exist or is inaccessible to anyone who might want to contribute. That's counter-productive; automated duplicate trackers shouldn't be allowed to take this kind of action that cannot be verified by the bug reporter.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.