I was trying to play an HD 720p *.mkv format video when this error happened.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: totem 3.10.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Mar 15 00:39:25 2014
ExecutablePath: /usr/bin/totem-video-thumbnailer
InstallationDate: Installed on 2014-03-14 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 file:///home/username/Downloads/Toy.Story.Trilogy.1995-2010.720p.BluRay.x264-PublicHD/Toy.Story.1995.720p.BluRay.x264-BestHD.mkv /tmp/.gnome_desktop_thumbnail.GB65CX
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f73c3a50297 <g_slice_alloc+167>: mov (%rbx),%rax
PC (0x7f73c3a50297) ok
source "(%rbx)" (0x200000000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
Title: totem-video-thumbnailer crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1289125, 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.