Bug 564884 – deadlock/hang in vee_freeze

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 564884 - deadlock/hang in vee_freeze


Summary:	deadlock/hang in vee_freeze


Status:	RESOLVED INCOMPLETE

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.24.x (obsolete)
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:	evolution[vfolders]

Depends on:
Blocks:

Reported:	2008-12-17 17:56 UTC by Brian J. Murrell
Modified:	2010-05-10 04:42 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description Brian J. Murrell 2008-12-17 17:56:52 UTC

Steps to reproduce:
No idea.  It just happened spontaneously.


Stack trace:

+ Trace 210892

Thread 1 (Thread 0xb6410940 (LWP 17840))

#0 __kernel_vsyscall
#1 __lll_lock_wait
from /lib/tls/i686/cmov/libpthread.so.0
#2 _L_lock_89
from /lib/tls/i686/cmov/libpthread.so.0
#3 pthread_mutex_lock
from /lib/tls/i686/cmov/libpthread.so.0
#4 vee_freeze
at camel-vee-folder.c line 1901
#5 camel_folder_freeze
at camel-folder.c line 1691
#6 emfv_delete_msg_response
at em-folder-view.c line 1082
#7 emfv_popup_delete
at em-folder-view.c line 1135
#8 ??
from /usr/lib/libbonoboui-2.so.0
#9 IA__g_closure_invoke
at /build/buildd/glib2.0-2.18.2/gobject/gclosure.c line 767
#10 bonobo_closure_invoke_va_list
from /usr/lib/libbonobo-2.so.0
#11 bonobo_closure_invoke
from /usr/lib/libbonobo-2.so.0
#12 ??
from /usr/lib/libbonoboui-2.so.0
#13 _ORBIT_skel_small_Bonobo_UIComponent_execVerb
from /usr/lib/libbonobo-2.so.0
#14 ORBit_c_stub_invoke
at poa.c line 2636
#15 Bonobo_UIComponent_execVerb
from /usr/lib/libbonobo-2.so.0
#16 ??
from /usr/lib/libbonoboui-2.so.0
#17 IA__g_cclosure_marshal_VOID__POINTER
at /build/buildd/glib2.0-2.18.2/gobject/gmarshal.c line 601
#18 g_type_class_meta_marshal
at /build/buildd/glib2.0-2.18.2/gobject/gclosure.c line 878
#19 IA__g_closure_invoke
at /build/buildd/glib2.0-2.18.2/gobject/gclosure.c line 767
#20 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.18.2/gobject/gsignal.c line 3282
#21 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.18.2/gobject/gsignal.c line 2977
#22 IA__g_signal_emit
at /build/buildd/glib2.0-2.18.2/gobject/gsignal.c line 3034
#23 bonobo_ui_engine_emit_verb_on
from /usr/lib/libbonoboui-2.so.0
#24 bonobo_ui_sync_keys_binding_handle
from /usr/lib/libbonoboui-2.so.0
#25 ??
from /usr/lib/libbonoboui-2.so.0
#26 _gtk_marshal_BOOLEAN__BOXED
at /build/buildd/gtk+2.0-2.14.4/gtk/gtkmarshalers.c line 84
#27 g_type_class_meta_marshal
at /build/buildd/glib2.0-2.18.2/gobject/gclosure.c line 878
#28 IA__g_closure_invoke
at /build/buildd/glib2.0-2.18.2/gobject/gclosure.c line 767
#29 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.18.2/gobject/gsignal.c line 3282
#30 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.18.2/gobject/gsignal.c line 2987
#31 IA__g_signal_emit
at /build/buildd/glib2.0-2.18.2/gobject/gsignal.c line 3034
#32 gtk_widget_event_internal
at /build/buildd/gtk+2.0-2.14.4/gtk/gtkwidget.c line 4745
#33 IA__gtk_propagate_event
at /build/buildd/gtk+2.0-2.14.4/gtk/gtkmain.c line 2365
#34 IA__gtk_main_do_event
at /build/buildd/gtk+2.0-2.14.4/gtk/gtkmain.c line 1596
#35 gdk_event_dispatch
at /build/buildd/gtk+2.0-2.14.4/gdk/x11/gdkevents-x11.c line 2365
#36 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.18.2/glib/gmain.c line 2144
#37 g_main_context_iterate
at /build/buildd/glib2.0-2.18.2/glib/gmain.c line 2778
#38 IA__g_main_loop_run
at /build/buildd/glib2.0-2.18.2/glib/gmain.c line 2986
#39 bonobo_main
from /usr/lib/libbonobo-2.so.0
#40 main
at main.c line 689



Other information:

Comment 1 Paul Bolle 2008-12-18 01:14:57 UTC

How did you get this backtrace: did evolution crash, did you attach gdb, etc,?

Comment 2 Brian J. Murrell 2008-12-18 03:07:51 UTC

I typically run evolution from gdb given the number of crashes and hangs it experiences (which is many).

In this case, typically the UI will hang for a long period and I will ^C in gdb and "thread apply all bt full" to get the backtrace and attach it here.

Comment 3 Akhil Laddha 2009-09-08 04:10:17 UTC

Did you get similar hang anytime in 2.26.x ?

Comment 4 Brian J. Murrell 2009-09-08 05:33:19 UTC

(In reply to comment #3)
> Did you get similar hang anytime in 2.26.x ?

I can't recall specifically.

Comment 5 Akhil Laddha 2010-03-26 10:05:51 UTC

This version is no longer maintained, which means that it will not receive any
further security or bug fix updates.
The current stable GNOME and Evolution version is 2.30.

Can you please check again whether this issue still happens in Evolution 2.28
or 2.30 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.

Again thank you for reporting this bug and we are sorry it could not be fixed
for the version you originally used here.

Without feedback this report will be closed as INCOMPLETE in 6 weeks.

Comment 6 Akhil Laddha 2010-05-10 04:42:12 UTC

Closing this bug report as no further information has been provided. Please 
feel free to reopen the bug if the problem still occurs with a newer
version of GNOME 2.30.0 or later, thanks.