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

[howefield]

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

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: totem 3.10.1-1ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 9 22:17:14 2014
ExecutablePath: /usr/bin/totem-video-thumbnailer
InstallationDate: Installed on 2014-04-09 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409)
ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 file:///home/username/Videos/Movies/Captain%20America.mkv /tmp/.gnome_desktop_thumbnail.O2N3DX
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: 0x7fe5e8ca728a <g_slice_alloc+154>: mov 0x8(%rdx),%rbx
 PC (0x7fe5e8ca728a) ok
 source "0x8(%rdx)" (0x7fe5c83d) not located in a known VMA region (needed readable region)!
 destination "%rbx" 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 vboxusers

[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.