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

[Jeffrey Tees]

Ubuntu 14.04 on Acer Aspire One D260
Error occurred while nautilus was generating thumbnails for mkv files located in home directory.

Thumbnail generation slowed on one file then continued, then error dialog popped up. Files were around 300Mb each.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: libgstreamer1.0-0 1.2.3-1
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Mar 26 16:01:59 2014
ExecutablePath: /usr/bin/totem-video-thumbnailer
InstallationDate: Installed on 2014-02-28 (25 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140228)
ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 file:///home/username/Videos/K-ON!!/K-ON!!%20s01e07%20-%20Tea%20Party!.mkv /tmp/.gnome_desktop_thumbnail.2LFSDX
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f37e0e77bc5: mov 0x8(%rdx),%rax
 PC (0x7f37e0e77bc5) ok
 source "0x8(%rdx)" (0x7f37c01b) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gstreamer1.0
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so
 ?? () from /usr/lib/x86_64-linux-gnu/libavcodec.so.54
Title: totem-video-thumbnailer crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1290368, 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.