rhythmbox-metadata crashed with SIGSEGV in free()

[dobey]

Binary package hint: rhythmbox

Just started up rhythmbox today, and got this crash.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Aug 13 10:19:00 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
NonfreeKernelModules: nvidia
Package: rhythmbox 0.12.3-1ubuntu2
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x598d86c <free+92>: lock cmpxchg %ecx,(%esi)
 PC (0x0598d86c) ok
 source "%ecx" ok
 destination "(%esi)" (0x2c3e6562) 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
 IA__g_free (mem=0x84cbc08)
 ?? ()
 structure_foreach_wrapper (field_id=347, value=0x84d9164,
 gst_structure_foreach (structure=0x84d5c20,
Title: rhythmbox-metadata crashed with SIGSEGV in free()
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin audio cdrom couchdb dialout dip floppy libvirtd lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:*__GI___libc_free (mem=0x84cbc08) at malloc.c:3714
IA__g_free (mem=0x84cbc08)
rb_metadata_gst_load_tag (list=0x84d5c20,
structure_foreach_wrapper (field_id=347, value=0x84d9164,
gst_structure_foreach (structure=0x84d5c20,

[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.

[Pedro Villavicencio (pedro)]

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!.