GNOME Bugzilla – Bug 555262
evolution and pidgin hangs
Last modified: 2013-08-24 15:06:49 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
+ Trace 207834
Thread 1 (Thread 0xb629a940 (LWP 1463))
Other information: While I cannot reproduce this at will, it happens several times a day.
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?
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:
+ Trace 207835
Thread 1 (Thread 0xb7007720 (LWP 1402))
Looks like Bonobo dropped the client connection? Not sure.
(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.
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
(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?
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.
(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.
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.
(In reply to comment #7) > I don't use evolution any more, and haven't for several years now Closing this report.