totem crashed upon closing

[Majord51]

After watching a short video (MPEG4 format), I was closing the video player when the crash ocurred. This has happened to me twice.

Ubuntu 14.04

Totem version 3.10.1-1ubuntu4

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: totem 3.10.1-1ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Apr 4 21:05:25 2014
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2014-02-26 (37 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: totem /media/data/Downloads/martin.clunes.and.a.lion.called.mugie.hdtv.x264-c4tv-sample.mp4
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f16434f9bc5: mov 0x8(%rdx),%rax
 PC (0x7f16434f9bc5) ok
 source "0x8(%rdx)" (0x00007f1d) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
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 crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: Upgraded to trusty on 2014-03-24 (11 days ago)
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 #1290378, 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.