rhythmbox-metadata crashed with SIGSEGV

Bug #1229400 reported by Giuseppe Pistola
186
This bug affects 22 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

populating and indexing music folder

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
Date: Mon Sep 23 22:32:25 2013
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationDate: Installed on 2013-09-23 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130922)
MarkForUpload: True
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
SegvAnalysis:
 Segfault happened at: 0x7f7e325d7fd7: movzbl (%r10,%rcx,1),%r10d
 PC (0x7f7e325d7fd7) ok
 source "(%r10,%rcx,1)" (0x7f7f3c0aecc7) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Giuseppe Pistola (sheldon) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 h_getbits (N=8, bb=0x7f7e3c0aeca8) at ../../src/bitstream.h:290
 h_rewindNbits (bb=bb@entry=0x7f7e3c0aeca8, N=<optimized out>) at ../../src/bitstream.c:262
 III_huffman_decode (is=is@entry=0x7f7e4eefc830, si=si@entry=0x7f7e4eefa9f0, ch=ch@entry=0, gr=gr@entry=0, part2_start=part2_start@entry=0, tl=tl@entry=0x7f7e3c0a9be0) at ../../src/mp3-c.c:611
 c_decode_mp3 (tl=tl@entry=0x7f7e3c0a9be0) at ../../src/mp3-c.c:1721
 mp3tl_decode_frame (tl=0x7f7e3c0a9be0, samples=<optimized out>, bufsize=<optimized out>) at ../../src/mp3tl.c:564

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in rhythmbox (Ubuntu):
status: New → Confirmed
tags: added: trusty
tags: added: bugpattern-needed
information type: Private → Public
TimoW (es-uomikim)
no longer affects: firefox (Ubuntu)
Revision history for this message
Simon Déziel (sdeziel) wrote :

I get that crash every time I start rhythmbox on Trusty. If more information is needed about this crash, please let me know.

Revision history for this message
Grzegorz G. (grzesiek1e5) wrote :

Fluendo's mp3 decoder crashes. The same issue affects e.g. Firefox.

Revision history for this message
angus73 (angus73) wrote :

It's not clear to me what are the drawbacks of this bug... I mean, after the crash rhythmbox seems to keep on working fine, so I would like to know what does not.

BTW, the bug also affects me on Ubuntu 14.04. When I run rhythmbox (but only the first time in a session, it seems), the rhythmbox-client crash window appears.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.