rhythmbox crashed with SIGSEGV in oil_init()

[TenLeftFingers]

I launched an mp3 (which played fine earlier today) from nautilus. Rhythmbox appeared briefly and then was replaced with a dialog reporting an error.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sun Oct 6 19:59:18 2013
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2013-10-02 (4 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta i386 (20130925.1)
MarkForUpload: True
ProcCmdline: rhythmbox /home/username/Music/Marconi\ Union\ -\ Weightless.mp3
ProcEnviron:
 LANGUAGE=en_IE:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xa0347e28: mov 0x10(%eax),%edx
 PC (0xa0347e28) ok
 source "0x10(%eax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/liboil-0.3.so.0
 oil_init () from /usr/lib/i386-linux-gnu/liboil-0.3.so.0
 ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstflump3dec.so
Title: rhythmbox crashed with SIGSEGV in oil_init()
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 #1226807, 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.