[Bug 50392] Re: gnome-panel uses 80% cpu after changing launchers properties

antoine antoine.conan at gmail.com
Tue Jun 20 21:34:54 UTC 2006


Hi ! here is a backtrace of the hang (<-- new word for me :p ) :

#0  0xb7880d7a in g_object_set_data () from /usr/lib/libgobject-2.0.so.0
#1  0xb7b05263 in gtk_label_get_width_chars ()
   from /usr/lib/libgtk-x11-2.0.so.0
#2  0xb7889db7 in g_cclosure_marshal_VOID__OBJECT ()
   from /usr/lib/libgobject-2.0.so.0
#3  0xb787d16f in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0
#4  0xb787d79f in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#5  0xb788c9ce in g_signal_stop_emission ()
   from /usr/lib/libgobject-2.0.so.0
#6  0xb788db19 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#7  0xb788de89 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#8  0xb7bfc19c in gtk_widget_set_parent_window ()
   from /usr/lib/libgtk-x11-2.0.so.0
#9  0xb7a528ab in gtk_bin_get_type () from /usr/lib/libgtk-x11-2.0.so.0
#10 0xb7a8ec46 in gtk_container_forall () from /usr/lib/libgtk-x11-2.0.so.0
#11 0xb7bfc1e4 in gtk_widget_set_parent_window ()
   from /usr/lib/libgtk-x11-2.0.so.0
#12 0xb7bfc6ed in _gtk_widget_propagate_hierarchy_changed ()
   from /usr/lib/libgtk-x11-2.0.so.0
#13 0xb7bfc87d in gtk_widget_unparent () from /usr/lib/libgtk-x11-2.0.so.0
#14 0xb7b0decc in gtk_list_clear_items () from /usr/lib/libgtk-x11-2.0.so.0
#15 0xb7a843cf in gtk_combo_set_popdown_strings ()
   from /usr/lib/libgtk-x11-2.0.so.0
#16 0xb7f27cfb in gnome_entry_set_history_id ()
   from /usr/lib/libgnomeui-2.so.0
#17 0xb7f27e95 in gnome_entry_set_history_id ()
   from /usr/lib/libgnomeui-2.so.0
#18 0xb7f27f45 in gnome_entry_set_history_id ()
   from /usr/lib/libgnomeui-2.so.0
#19 0xb7d59277 in gconf_client_change_set_from_current ()
#20 0xb7d499f0 in gconf_listeners_notify () from /usr/lib/libgconf-2.so.4
#21 0xb7d59337 in gconf_client_change_set_from_current ()
   from /usr/lib/libgconf-2.so.4
#22 0xb7d59523 in gconf_client_notify () from /usr/lib/libgconf-2.so.4
#23 0xb7815bf2 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0
#24 0xb78138d6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb7816996 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#26 0xb7816cb8 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#27 0xb7b16775 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#28 0x080668fb in main (argc=80, argv=0x50)
    at /build/buildd/gnome-panel-2.14.2/./gnome-panel/main.c:92

This can happen with any of my launchers (I only have seven of them :
aoss firefox %u ; amule ; gksu /usr/sbin/synaptic ; xsane ; gimp-
remote-2.2 %U ; vmplayer ; gedit %U), but you have to combine at least
two "right-click > properties > close" actions.

The hang above happenned with the deadly "firefox-synaptic" sequence. It
won't happen if you repeatedly open/close the properties dialog-box of
the same launcher.

-- 
gnome-panel uses 80% cpu after changing launchers properties
https://launchpad.net/bugs/50392




More information about the desktop-bugs mailing list