rhythmbox-metadata crashed with SIGSEGV in free()

[Leif Walsh]

Binary package hint: rhythmbox

Crash occurred during a scan of my external hard drive. Rhythmbox itself did not crash (the window, at least), and the scan completed just fine. The only detectable problem was that apport notified me. Not sure if this is important for now.

$ lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10
$ apt-cache policy rhythmbox
rhythmbox:
  Installed: 0.12.3-1ubuntu1
  Candidate: 0.12.3-1ubuntu1
  Version table:
 *** 0.12.3-1ubuntu1 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Aug 3 04:14:26 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
Package: rhythmbox 0.12.3-1ubuntu1
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SegvAnalysis:
 Segfault happened at: 0xb72f3dd0 <free+128>: lock cmpxchg %ecx,(%esi)
 PC (0xb72f3dd0) ok
 source "%ecx" ok
 destination "(%esi)" (0x6c796170) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 free () from /lib/tls/i686/cmov/libc.so.6
 g_free () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? () from /usr/lib/libgstreamer-0.10.so.0
 gst_structure_foreach () from /usr/lib/libgstreamer-0.10.so.0
Title: rhythmbox-metadata crashed with SIGSEGV in free()
Uname: Linux 2.6.31-4-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:*__GI___libc_free (mem=0x86bbc48) at malloc.c:3623
IA__g_free (mem=0x86bbc48)
rb_metadata_gst_load_tag (list=0x86bc420,
structure_foreach_wrapper (field_id=343, value=0x8616b7c,
gst_structure_foreach (structure=0x86bc420,

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Leif Walsh (leif.walsh)]

To trigger the bug, I need to start rhythmbox with my external hard drive unmounted, let it remove everything from its library, kill rhythmbox, mount the drive, and restart it. During the scan, it crashes.

I ran rhythmbox in valgrind as requested, and attached the log. I killed it after about an hour, since valgrind makes it so incredibly slow. If you can make sense of what's there, that's great, otherwise, let me know and I'll re-run it overnight and get the full log.

[Andrea Caminiti (nrayever)]

Happend to me too. it happend when rhythmbox was scanning my external hard-drive too.

Regards, Andrea

[Nipas (nik8pol)]

Happened to me too . I want to add that i have an amd64 system so this is not a bug concerning only i386 systems

[Cousteau (war-richard)]

Happened to me too, but I'm on lucid lynx (updated as of 12th of Jan 2010).

[Russ W. Knize (rknize)]

I am seeing this issue as well after upgrading to lucid lynx from hardy (last update 03/24/2010). Rhythmbox becomes unresponsive shortly after startup and rhythmbox-metadata pegs the CPU while it spits out backtraces about bad free()s. The tracks are on an external USB hard drive.

[Pedro Villavicencio (pedro)]

could you please install the libgstreamer dbgsym packages and also the rhythmbox ones? the valgrind log is missing a lot of symbols, thanks in advance.

[Victor Vargas (kamus)]

Please could you attach the information that Pedro is asking running latest release of Ubuntu? Thanks

[Omer Akram (om26er)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!