rhythmbox crashed with SIGSEGV in g_type_check_instance_is_a()

[petrux]

I was just listening to some music with the application minimzed in the upper bar. I had manually deleted some tracks which were about to be played from the media library (but I don't know if this could be related).

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.4-0ubuntu1~ubuntu14.04.1~c42.ppa1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Thu Nov 13 16:13:57 2014
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2014-01-10 (307 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: rhythmbox
SegvAnalysis:
 Segfault happened at: 0x7fc6a210dd6c <g_type_check_instance_is_a+60>: testb $0x4,0x16(%r8)
 PC (0x7fc6a210dd6c) ok
 source "$0x4" ok
 destination "0x16(%r8)" (0x646f63656469728a) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 gst_pad_link_full () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstplayback.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in g_type_check_instance_is_a()
UpgradeStatus: Upgraded to trusty on 2014-10-15 (29 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 #1351103, 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.