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 555262 - evolution and pidgin hangs
evolution and pidgin hangs
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-10-06 16:41 UTC by Brian J. Murrell
Modified: 2013-08-24 15:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Brian J. Murrell 2008-10-06 16:41:38 UTC
Steps to reproduce:
I have evolution and pidgin running on my machine with pidgin configured to sync to evolution.  Every day, several times a day evolution will hang, then shortly afterward pidgin will hang.  I have to use evolution --force-shutdown to get evolution to quit and pidgin to "come back to life".  I suspect this is some kind of deadlock in the data server back end.

Stack trace:
Stack traces of evolution threads:

(gdb) thread apply all bt

Thread 1 (Thread 0xb629a940 (LWP 1463))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_context_iterate
    at /build/buildd/glib2.0-2.18.1/glib/gmain.c line 3089
  • #3 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.18.1/glib/gmain.c line 2984
  • #4 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #5 main
    at main.c line 689
  • #0 __kernel_vsyscall
  • #0 ??
    from /lib/ld-linux.so.2
  • #1 pthread_cond_wait
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 giop_recv_buffer_get
    at giop-recv-buffer.c line 716
  • #3 ORBit_small_invoke_stub
    at orbit-small.c line 660
  • #4 ORBit_small_invoke_stub_n
    at orbit-small.c line 577
  • #5 ORBit_c_stub_invoke
    at poa.c line 2649
  • #6 GNOME_Evolution_Addressbook_BookFactory_getBook
    at Evolution-DataServer-Addressbook-stubs.c line 330
  • #7 e_book_new
    at e-book.c line 3271
  • #8 e_book_new_from_uri
    at e-book.c line 3787
  • #9 gevo_load_addressbook
    at ../../../../pidgin/plugins/gevolution/gevo-util.c line 144
  • #10 gevo_run_query_in_uri
    at ../../../../pidgin/plugins/gevolution/eds-utils.c line 123
  • #11 gevo_search_buddy_in_contacts
    at ../../../../pidgin/plugins/gevolution/eds-utils.c line 232
  • #12 blist_node_extended_menu_cb
    at ../../../../pidgin/plugins/gevolution/gevolution.c line 271
  • #13 purple_marshal_VOID__POINTER_POINTER
    at ../../libpurple/signals.c line 669
  • #14 purple_signal_emit_vargs
    at ../../libpurple/signals.c line 482
  • #15 purple_signal_emit
    at ../../libpurple/signals.c line 434
  • #16 purple_blist_node_get_extended_menu
    at ../../libpurple/blist.c line 2686
  • #17 pidgin_append_blist_node_extended_menu
    at ../../pidgin/gtkblist.c line 1380
  • #18 populate_menu_with_options
    at ../../pidgin/gtkconv.c line 3233
  • #19 regenerate_options_items
    at ../../pidgin/gtkconv.c line 3263
  • #20 switch_conv_cb
    at ../../pidgin/gtkconv.c line 8884
  • #21 _gtk_marshal_VOID__POINTER_UINT
    at /build/buildd/gtk+2.0-2.14.3/gtk/gtkmarshalers.c line 2582
  • #22 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.18.1/gobject/gclosure.c line 767
  • #23 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.18.1/gobject/gsignal.c line 3314
  • #24 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.18.1/gobject/gsignal.c line 2977
  • #25 IA__g_signal_emit
    at /build/buildd/glib2.0-2.18.1/gobject/gsignal.c line 3034
  • #26 gtk_notebook_switch_page
    at /build/buildd/gtk+2.0-2.14.3/gtk/gtknotebook.c line 5826
  • #27 gtk_notebook_button_press
    at /build/buildd/gtk+2.0-2.14.3/gtk/gtknotebook.c line 2517
  • #28 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.14.3/gtk/gtkmarshalers.c line 84
  • #29 g_type_class_meta_marshal
    at /build/buildd/glib2.0-2.18.1/gobject/gclosure.c line 878
  • #30 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.18.1/gobject/gclosure.c line 767
  • #31 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.18.1/gobject/gsignal.c line 3282
  • #32 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.18.1/gobject/gsignal.c line 2987
  • #33 IA__g_signal_emit
    at /build/buildd/glib2.0-2.18.1/gobject/gsignal.c line 3034
  • #34 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.14.3/gtk/gtkwidget.c line 4745
  • #35 IA__gtk_propagate_event
    at /build/buildd/gtk+2.0-2.14.3/gtk/gtkmain.c line 2391
  • #36 IA__gtk_main_do_event
    at /build/buildd/gtk+2.0-2.14.3/gtk/gtkmain.c line 1581
  • #37 gdk_event_dispatch
    at /build/buildd/gtk+2.0-2.14.3/gdk/x11/gdkevents-x11.c line 2365
  • #38 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.18.1/glib/gmain.c line 2142
  • #39 g_main_context_iterate
    at /build/buildd/glib2.0-2.18.1/glib/gmain.c line 2776
  • #40 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.18.1/glib/gmain.c line 2984
  • #41 IA__gtk_main
    at /build/buildd/gtk+2.0-2.14.3/gtk/gtkmain.c line 1200
  • #42 main
    at ../../pidgin/gtkmain.c line 887


Other information:
While I cannot reproduce this at will, it happens several times a day.
Comment 1 Matthew Barnes 2008-10-06 17:33:13 UTC
I think you're right.  Both clients are trying to open an address book but it looks like evolution-data-server died (see Thread 1).

Can you try to capture a stacktrace of evolution-data-server so we can see where it's crashing?  Easiest way is to start Evolution normally and connect GDB to the evolution-data-server process before it dies, like so:

   $ ps ax | grep evolution-data-server

   Note the process ID (first number) of evolution-data-server.

   $ gdb --pid <process-id>
   ...
   (gdb) continue

   Then just wait for it to happen again.

Also, can you elaborate on what "hang" means here?  Is the UI unresponsive, such that dragging another window over Evolution causes Evolution to not repaint itself correctly?  Or can you click things in the UI but nothing happens?
Comment 2 Matthew Barnes 2008-10-06 17:39:14 UTC
Oops, I'm sorry.  I missed the evolution-data-server stacktrace that you already provided.  Thread 1 in the e-d-s stacktrace looks important:

Thread 1 (Thread 0xb7007720 (LWP 1402))

  • #4 e_book_backend_remove_client
    at e-book-backend.c line 598
  • #5 listener_died_cb
    at e-book-backend.c line 484
  • #6 link_connection_emit_broken
    at linc-connection.c line 146
  • #7 link_connection_broken_idle
    at linc-connection.c line 183

Looks like Bonobo dropped the client connection?  Not sure.
Comment 3 Brian J. Murrell 2008-10-06 18:36:40 UTC
(In reply to comment #2)
> 
> Looks like Bonobo dropped the client connection?  Not sure.

Anything further I can do to help debug, just let me know.  Like I said, it happens pretty regularly here. 

Comment 4 Srinivasa Ragavan 2008-10-07 09:03:16 UTC
Oh wait, IIRC Michael Meeks poked me for one such issue to tell me that it might have to do with orbit.

https://bugzilla.novell.com/show_bug.cgi?id=393634 Not sure, if this bug is visible outside.

===
Srini - it's possible this is the underlying problem in some of the evolution
deadlocks as well: around broken connectionness:

if you see a ORBit_foo_try_reconnect in one thread and a
link_emit_broken_callbacks in another - it's prolly a dup.
===


I see a similar issue here
Comment 5 Brian J. Murrell 2008-10-07 10:28:53 UTC
(In reply to comment #4)
> 
> https://bugzilla.novell.com/show_bug.cgi?id=393634 Not sure, if this bug is
> visible outside.

This bug was closed 2008-05-23.  Surely it landed on Gnome 2.24, no?
Comment 6 André Klapper 2012-06-18 10:37:52 UTC
Hi gnome-bugs, 
if you have time, could you please check again whether this issue still happens in Evolution 3.4.2 or 3.2.3 and update this report by adding a comment and changing the "Version" field and provide information about your distribution? Thanks a lot.
Comment 7 Brian J. Murrell 2012-06-18 10:51:08 UTC
(In reply to comment #6)
> Hi gnome-bugs, 

Hi,

> if you have time, could you please check again whether this issue still happens
> in Evolution 3.4.2 or 3.2.3 and update this report by adding a comment and
> changing the "Version" field and provide information about your distribution?
> Thanks a lot.

I don't use evolution any more, and haven't for several years now due to the mounting list of bugs that were preventing daily use due to hangs, crashes and excessive memory usage (leaking).

I'm a (not so happy) Thunderbird user now.  It has it's problems also, but they are less severe than Evolutions were when I last used it.
Comment 8 Brian J. Murrell 2012-06-18 10:56:15 UTC
I should add that I do have infrequent occasion to use evolution on a laptop I have around here and even 3.2.3 is still leaking memory like a sieve.  Looking at it right now, it's 3.5GB of VM for 2 IMAP accounts started in the last 24 hours or so.  It will continue to grow in usage until I kill it.
Comment 9 André Klapper 2013-08-24 15:06:49 UTC
(In reply to comment #7)
> I don't use evolution any more, and haven't for several years now

Closing this report.