totem-video-thumbnailer crashed with SIGSEGV in magazine_chain_pop_head()

[Angel Guzman Maeso]

This crash is produced by totem trying to open a .mkv video (it could be downloaded via torrent)

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: libgstreamer1.0-0 1.2.3-1
Uname: Linux 3.13.0-031300rc1-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CurrentDesktop: Unity
Date: Wed Mar 12 16:05:45 2014
ExecutablePath: /usr/bin/totem-video-thumbnailer
InstallationDate: Installed on 2013-02-03 (402 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 file:///SteamLibrary/Cosmos.A.Space.Time.Odyssey.S01E01.720p.HDTV.X264-DIMENSION.mkv /tmp/.gnome_desktop_thumbnail.0UC4CX
SegvAnalysis:
 Segfault happened at: 0xb6bf72de <g_slice_alloc+158>: mov (%edi),%edx
 PC (0xb6bf72de) ok
 source "(%edi)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gstreamer1.0
StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0xb1f00508) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:539
 thread_memory_magazine1_alloc (tmem=<optimized out>, ix=19) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:842
 g_slice_alloc (mem_size=mem_size@entry=156) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:998
 g_slice_alloc0 (mem_size=156) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:1032
 ?? () from /usr/lib/i386-linux-gnu/libgstvideo-1.0.so.0
Title: totem-video-thumbnailer crashed with SIGSEGV in magazine_chain_pop_head()
UpgradeStatus: Upgraded to trusty on 2013-10-31 (132 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

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.