GNOME Bugzilla – Bug 636322
rhythmbox assert failure: *** glibc detected *** /usr/bin/rhythmbox: corrupted double-linked list: 0x00007f46306757d0 ***
Last modified: 2010-12-29 23:28:56 UTC
Open bug in launchpad.net: https://bugs.launchpad.net/bugs/684400 "Open Banshee Close Banshee Open Rhythmbox Close Rhythmbox Open Apport -> 100% Reproducible"
+ Trace 224941
Valgrind: "==15838== Invalid read of size 4 ==15838== at 0x9DD26BE: PyObject_Realloc (obmalloc.c:1154) ==15838== by 0x9E5F1D8: _PyObject_GC_Resize (gcmodule.c:1396) ==15838== by 0x9DB788C: PyFrame_New (frameobject.c:655) ==15838== by 0x9E313B2: PyEval_EvalFrameEx (ceval.c:3825) ==15838== by 0x9E31467: PyEval_EvalFrameEx (ceval.c:3836) ==15838== by 0x9E31467: PyEval_EvalFrameEx (ceval.c:3836) ==15838== by 0x9E31467: PyEval_EvalFrameEx (ceval.c:3836) ==15838== by 0x9E328AF: PyEval_EvalCodeEx (ceval.c:3000) ==15838== by 0x9E30BEA: PyEval_EvalFrameEx (ceval.c:3846) ==15838== by 0x9E328AF: PyEval_EvalCodeEx (ceval.c:3000) ==15838== by 0x9E30BEA: PyEval_EvalFrameEx (ceval.c:3846) ==15838== by 0x9E328AF: PyEval_EvalCodeEx (ceval.c:3000) ==15838== by 0x9E30BEA: PyEval_EvalFrameEx (ceval.c:3846) ==15838== by 0x9E328AF: PyEval_EvalCodeEx (ceval.c:3000) ==15838== by 0x9DB862F: function_call (funcobject.c:524) ==15838== by 0x9D8ABB2: PyObject_Call (abstract.c:2492) ==15838== by 0x9D9C5BE: instancemethod_call (classobject.c:2579) ==15838== by 0x9D8ABB2: PyObject_Call (abstract.c:2492) ==15838== by 0x9DF166F: slot_tp_init (typeobject.c:5632) ==15838== by 0x9DE7957: type_call (typeobject.c:742) ==15838== by 0x9D8ABB2: PyObject_Call (abstract.c:2492) ==15838== by 0x9D8ED25: PyObject_CallFunctionObjArgs (abstract.c:2723) ==15838== by 0x9E2D713: PyEval_EvalFrameEx (ceval.c:4361) ==15838== by 0x9E328AF: PyEval_EvalCodeEx (ceval.c:3000) ==15838== by 0x9E32981: PyEval_EvalCode (ceval.c:541) ==15838== by 0x9E43DD1: PyImport_ExecCodeModuleEx (import.c:677) ==15838== by 0x9E4671D: load_source_module (import.c:1017) ==15838== by 0x9E475C4: import_submodule (import.c:2592) ==15838== by 0x9E47843: load_next (import.c:2412) ==15838== by 0x9E47EA4: import_module_level (import.c:2133) ==15838== by 0x9E48403: PyImport_ImportModuleLevel (import.c:2185) ==15838== by 0x9E2A76E: builtin___import__ (bltinmodule.c:48) ==15838== by 0x9D8ABB2: PyObject_Call (abstract.c:2492) ==15838== by 0x9E2ACC2: PyEval_CallObjectWithKeywords (ceval.c:3619) ==15838== by 0x9E2E777: PyEval_EvalFrameEx (ceval.c:2159) ==15838== by 0x9E328AF: PyEval_EvalCodeEx (ceval.c:3000) ==15838== by 0x9E32981: PyEval_EvalCode (ceval.c:541) ==15838== by 0x9E43DD1: PyImport_ExecCodeModuleEx (import.c:677) ==15838== by 0x9E4671D: load_source_module (import.c:1017) ==15838== by 0x9E475C4: import_submodule (import.c:2592) ==15838== Address 0x1b52d020 is not stack'd, malloc'd or (recently) free'd" https://bugs.launchpad.net/rhythmbox/+bug/684400/+attachment/1753390/+files/valgrind2.log.lzma
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Jonathan: What symbols?
Created attachment 175751 [details] Valgrind4.log
. Hilo 6 (Thread 12637):
+ Trace 224960
ping =)
Valgrind output would be useful here, but the valgrind output you have provided shows a completely different problem.
Problem: 1) Open Rhythmbox 2) add many files 3) Close rhythmbox (not full load files) 4) Open apport