Bug 439793 – Crash in deregister_application()

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 439793 - Crash in deregister_application()


Summary:	Crash in deregister_application()


Status:	RESOLVED DUPLICATE of bug 446574

Product:	at-spi
Classification:	Platform
Component:	general
Version:	unspecified
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	Li Yuan
QA Contact:	Li Yuan

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-19 22:14 UTC by Vincent Untz
Modified:	2008-11-14 03:34 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Vincent Untz 2007-05-19 22:14:00 UTC

(I don't know if I should file the bug against atk or at-spi)

I'm getting a lot of crashes while playing with 2.19. I'm not sure I have the latest trunk for accessibility stuff, but it's at least 2.19.

(gdb) bt

+ Trace 135087

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 865
#3 <signal handler called>
#4 IA__g_logv
at gmessages.c line 493
#5 IA__g_log
at gmessages.c line 517
#6 IA__g_return_if_fail_warning
#7 bonobo_object_corba_objref
at bonobo-object.c line 1226
#8 deregister_application
at bridge.c line 591
#9 spi_atk_bridge_toplevel_removed
at bridge.c line 316
#10 IA__g_cclosure_marshal_VOID__UINT_POINTER
#11 IA__g_closure_invoke
at gclosure.c line 490
#12 signal_emit_unlocked_R
at gsignal.c line 2440
#13 IA__g_signal_emit_valist
at gsignal.c line 2199
#14 IA__g_signal_emit_by_name
at gsignal.c line 2267
#15 _gail_toplevel_remove_child
at gailtoplevel.c line 340
#16 gail_toplevel_hide_event_watcher
at gailtoplevel.c line 309
#17 signal_emit_unlocked_R
at gsignal.c line 2406
#18 IA__g_signal_emit_valist
at gsignal.c line 2199
#19 IA__g_signal_emit
#20 IA__gtk_widget_hide
at gtkwidget.c line 2483
#21 IA__gtk_menu_popdown
at gtkmenu.c line 1488
#22 gtk_menu_deactivate
at gtkmenu.c line 3817
#23 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#24 g_type_class_meta_marshal
at gclosure.c line 567
#25 IA__g_closure_invoke
at gclosure.c line 490
#26 signal_emit_unlocked_R
at gsignal.c line 2370
#27 IA__g_signal_emit_valist
at gsignal.c line 2199
#28 IA__g_signal_emit
at gsignal.c line 2243
#29 IA__gtk_menu_shell_deactivate
at gtkmenushell.c line 471
#30 IA__gtk_menu_shell_activate_item
#31 gtk_menu_shell_button_release
at gtkmenushell.c line 645
#32 gtk_menu_button_release
at gtkmenu.c line 2713
#33 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#34 g_type_class_meta_marshal
at gclosure.c line 567
#35 IA__g_closure_invoke
at gclosure.c line 490
#36 signal_emit_unlocked_R
at gsignal.c line 2478
#37 IA__g_signal_emit_valist
at gsignal.c line 2209
#38 IA__g_signal_emit
at gsignal.c line 2243
#39 gtk_widget_event_internal
at gtkwidget.c line 4136
#40 IA__gtk_widget_event
at gtkwidget.c line 3937
#41 IA__gtk_propagate_event
at gtkmain.c line 2343
#42 IA__gtk_main_do_event
at gtkmain.c line 1563
#43 gdk_event_dispatch
at gdkevents-x11.c line 2321
#44 g_main_dispatch
at gmain.c line 2061
#45 IA__g_main_context_dispatch
at gmain.c line 2613
#46 g_main_context_iterate
at gmain.c line 2694
#47 IA__g_main_loop_run
at gmain.c line 2898
#48 bonobo_main
at bonobo-main.c line 311
#49 bonobo_generic_factory_main_timeout
at bonobo-generic-factory.c line 411
#50 bonobo_generic_factory_main
at bonobo-generic-factory.c line 368
#51 panel_applet_factory_main_closure
#52 panel_applet_factory_main
at panel-applet.c line 1781
#53 main
at wncklet.c line 212

Comment 1 Yi Jin 2007-05-23 07:03:35 UTC

It looks like a gnome-pannel's dump. 
Hi, Vincent, could you please provide the step list to reproduce it?

Comment 2 Vincent Untz 2007-05-23 12:14:02 UTC

It happens quite a lot, although I'm not sure how.

I'm running a GNOME built with jhbuild, and I just right-click a few times on an applet, or I open the calendar of the clock applet a few times, or the window selector a few times. It's easy to trigger for me.

Comment 3 Vincent Untz 2007-07-08 09:44:33 UTC

Hrm. It seems to be happening when at-spi-registryd is not running. Well, I'm not sure that's the same crash, but if you have a11y enabled but the registryd is not running, you get a crash when the context menu of an applet is closed.

Comment 4 Li Yuan 2007-09-13 02:47:23 UTC

Hi Vincent, is your at-spi-registryd crashed before? I think that's the root cause of the crash. Do you have a trace?

Comment 5 Vincent Untz 2007-09-13 09:37:13 UTC

Well, I don't know if at-spi-registryd crashed before since it was two months ago :-) But still, at-spi-registryd not running shouldn't make applications crash.

Comment 6 Li Yuan 2008-11-14 03:34:07 UTC


*** This bug has been marked as a duplicate of 446574 ***