GNOME Bugzilla – Bug 213431
Crash: evolution-mail deadlock/hang
Last modified: 2001-11-01 15:06:33 UTC
Package: Evolution Priority: Major Version: 0.15 Synopsis: evolution-mail deadlock/hang Bugzilla-Product: Evolution Bugzilla-Component: Mailer Description: Several times a day, evolution hangs solid (no refresh, no activity). This crash is the result of doing "killall -SEGV evolution-mail" in the hopes that it will give you some clue as to what is going on. Please let me know if there is anything more useful I can pass along. Debugging Information: [New Thread 1024 (LWP 2808)] [New Thread 2049 (LWP 2835)] 0x40b685c9 in __wait4 () from /lib/i686/libc.so.6
+ Trace 12290
Thread 1 (Thread 1024 (LWP 2808))
Unknown reporter: mthome@bbn.com, changed to bugbuddy-import@ximian.com.
Can you guys take a look at this?
First, i'd suggest updating. Second, this looks like bonobo or zlib.
what version of gnome-xml do you have installed?
Currently, I'm running with: bonobo-1.0.7-ximian.3 libbonobo-conf0-0.12-ximian.1 bonobo-devel-1.0.7-ximian.3 bonobo-conf-0.12-ximian.1 zlib-1.1.3-12 zlib-devel-1.1.3-12 libxml-devel-1.8.15-ximian.2 libxml-1.8.15-ximian.2 FYI, I'll also attach my *current* set of rpms. I'll also plan on doing a red-carpet update later today
Created attachment 40430 [details] [review] current set of rpms
I've done a red-carpet update. Here are the current versions of the above packages: bonobo-1.0.9-ximian.1 libbonobo-conf0-0.12-ximian.1 bonobo-devel-1.0.9-ximian.1 bonobo-conf-0.12-ximian.1 zlib-1.1.3-12 zlib-devel-1.1.3-12 libxml-devel-1.8.15-ximian.2 libxml-1.8.15-ximian.2 evolution-0.16-ximian.2 see bug 213620 for a post-update crash done the same way. Additional info - it seems to most often occur after reading a message in one folder and then selecting a different folder.
*** bug 213620 has been marked as a duplicate of this bug. ***
Can you attach with gdb instead of usihng SEGV? Need to find out if its looping, or waiting for non-existant resources. But unless you know how to drive gdb, i can't see how we can do this.
Created attachment 40463 [details] ps, gdb bt/threads of various procs
looks like etable?
gnome-xml bug.
more specific, Chris? Is this a *fixed* gnome-xml bug? And if not, is it workaroundable? And has it been reported?
Could this be due to libxml as non-thread-safe? libxml2.4.7 is the first version which claims to be thread safe. If evolution is parsing in parallel, it could easily explain the visible behavior. If this is the problem, it could certainly be viewed as a ximian bug (use of a lib in an unsupported way). In any case, if ximian cannot resolve the bug, you'll at least need to document evolution as being unstable in SMP environments.