rhythmbox-metadata crashed with SIGSEGV

[Jonathan Brier]

rhythm box was extracting a cd in FLAC format to the music folder when on track 8 of 10 this crash report appeared. CD in process was Nickel Creek A Dotted Line

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.1-1ubuntu16
ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
Uname: Linux 3.13.0-21-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 2 17:40:03 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationDate: Installed on 2012-11-29 (489 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2d8ccb2fd7: movzbl (%r10,%rcx,1),%r10d
 PC (0x7f2d8ccb2fd7) ok
 source "(%r10,%rcx,1)" (0x7f2e3c0330e7) not located in a known VMA region (needed readable region)!
 destination "%r10d" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
Title: rhythmbox-metadata crashed with SIGSEGV
UpgradeStatus: Upgraded to trusty on 2014-03-28 (4 days ago)
UserGroups: adm cdrom dip lpadmin plex 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 #1229400, 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.