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 640106 - Assertion fails on exit when signal hook is present and appears-as-list=1
Assertion fails on exit when signal hook is present and appears-as-list=1
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkComboBox
2.22.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2011-01-20 20:42 UTC by Ruslan Kabatsayev
Modified: 2018-05-02 15:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Test program (935 bytes, text/plain)
2011-01-20 20:43 UTC, Ruslan Kabatsayev
Details

Description Ruslan Kabatsayev 2011-01-20 20:42:52 UTC
I get these errors when the window of the program attached is closed:


(test:9906): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed

(test:9906): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed

This is only when GtkComboBox::appears-as-list=1 is set in gtkrc.
Comment 1 Ruslan Kabatsayev 2011-01-20 20:43:18 UTC
Created attachment 178884 [details]
Test program
Comment 2 Daniel Boles 2017-08-24 00:46:03 UTC
If you can still reproduce this (I assume yes), it would be great if you had posted a backtrace with debug symbols to each critical.
Comment 3 Daniel Boles 2017-08-24 01:32:55 UTC
I can't reproduce this on GTK+ 3. In contrast, I can on GTK+ 2, but I don't have a debug version of that immediately available, so the backtrace I got is useless.
Comment 4 Daniel Boles 2017-08-24 07:30:37 UTC
This system has a slightly less useless GTK+ 2 build, but still not much help.


(a.out:22187): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed

Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007ffff5e5c481 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
(ins)(gdb) bt
  • #0 ??
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #1 g_logv
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #2 g_log
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #3 g_object_ref
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #4 ??
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #5 g_signal_emit_valist
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #6 g_signal_emit
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #7 gtk_widget_unparent
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #8 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #9 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #10 g_object_unref
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #12 g_closure_invoke
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #17 g_object_run_dispose
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #18 gtk_main_do_event
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
  • #20 g_main_context_dispatch
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #21 ??
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #24 main
    at /tmp/2-test.c line 29
  • #0 ??
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #1 g_logv
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #2 g_log
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #3 g_object_ref
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #4 ??
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #5 g_signal_emit_valist
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #6 g_signal_emit
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #7 gtk_widget_unparent
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #8 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #9 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #10 g_object_unref
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #12 g_closure_invoke
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #17 g_object_run_dispose
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #18 gtk_main_do_event
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
  • #20 g_main_context_dispatch
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #21 ??
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  • #24 main
    at /tmp/2-test.c line 29

Comment 5 GNOME Infrastructure Team 2018-05-02 15:01:08 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/349.