After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 422982 - rhythmbox-metadata crashed with SIGSEGV in object_remove_closure()
rhythmbox-metadata crashed with SIGSEGV in object_remove_closure()
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.x
Other Linux
: Normal critical
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-26 12:48 UTC by Sebastien Bacher
Modified: 2009-04-15 22:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Sebastien Bacher 2007-03-26 12:48:52 UTC
The bug has been described on https://launchpad.net/bugs/95846

"Binary package hint: rhythmbox

rhythmbox was in "standby" and crashed while indexing the metadata of my music files.

ProblemType: Crash
Architecture: i386
Date: Sun Mar 25 10:52:36 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
Package: rhythmbox 0.9.8-0ubuntu2 [modified: usr/lib/rhythmbox/rhythmbox-metadata usr/lib/librhythmbox-core.so.0.0.0 usr/bin/rhythmbox usr/bin/rhythmbox-client]
PackageArchitecture: i386
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
...
.

Thread 5 (process 13053)

  • #0 handler_insert
    at ../glib/gbsearcharray.h line 202
  • #1 IA__g_signal_connect_closure
    at gsignal.c line 1611
  • #2 IA__g_signal_connect_object
    at gobject.c line 2077
  • #3 rb_metadata_load
    at rb-metadata-gst.c line 1053
  • #4 _handle_message
    at rb-metadata-dbus-service.c line 117
  • #5 _dbus_object_tree_dispatch_and_unlock
    at dbus-object-tree.c line 842
  • #6 dbus_connection_dispatch
    at dbus-connection.c line 4308
  • #7 message_queue_dispatch
    at dbus-gmain.c line 101
  • #8 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #9 g_main_context_iterate
    at gmain.c line 2677
  • #10 IA__g_main_loop_run
    at gmain.c line 2881
  • #11 main
    at rb-metadata-dbus-service.c line 504

Thread 1 (process 13460)

  • #0 object_remove_closure
    at gobject.c line 2115
  • #1 IA__g_closure_invalidate
    at gclosure.c line 166
  • #2 IA__g_closure_unref
    at gclosure.c line 392
  • #3 IA__g_signal_handlers_destroy
    at gsignal.c line 578
  • #4 g_object_real_dispose
    at gobject.c line 532
  • #5 gst_object_dispose
    at gstobject.c line 446
  • #6 gst_element_dispose
    at gstelement.c line 2606
  • #7 gst_bin_dispose
    at gstbin.c line 453
  • #8 gst_decode_bin_dispose
    at gstdecodebin.c line 370
  • #9 IA__g_object_unref
    at gobject.c line 1760
  • #10 gst_object_unref
    at gstobject.c line 354
  • #11 gst_bin_remove_func
    at gstbin.c line 988
  • #12 gst_bin_remove
    at gstbin.c line 1045
  • #13 gst_bin_dispose
    at gstbin.c line 446
  • #14 gst_pipeline_dispose
    at gstpipeline.c line 273
  • #15 IA__g_object_unref
    at gobject.c line 1760
  • #16 gst_object_unref
    at gstobject.c line 354
  • #17 gst_bin_recalc_func
    at gstbin.c line 2076
  • #18 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #19 g_thread_create_proxy
    at gthread.c line 591
  • #20 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #21 clone
    from /lib/tls/i686/cmov/libc.so.6"

Comment 1 Sebastien Bacher 2007-08-06 09:58:28 UTC
Similar backtrace on https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/125688
Comment 2 Tim-Philipp Müller 2009-04-15 22:14:37 UTC
Wow, this is old. Seeing that there haven't been any duplicates, let's assume this issue has been fixed. Please re-open if the issue still exists with newer versions of things. Looks like a refcount bug somewhere or maybe an issue in gobject to me.

Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.