GNOME Bugzilla – Bug 308791
64 bit: Random crashes (thread related?)
Last modified: 2005-08-19 13:21:33 UTC
Distribution: Fedora Core release 4 (Stentz) Package: Evolution Severity: normal Version: GNOME2.10.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Random crashes (thread related?) Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Evolution crashes at random times -- usually in response to clicking on "something". Steps to reproduce the crash: 1. Unknown Expected Results: No crash. How often does this happen? 2-3 times a day under general mail usage. I use an IMAP server. Additional Information: My system is a dual-processor Xeon running fedora core 4 x86_64. Due to the seemingly random nature of the crashes, my guess is that this a thread-related issue. Debugging Information: Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912496356672 (LWP 28474)] [New Thread 1169213792 (LWP 29081)] [New Thread 1168947552 (LWP 29080)] [New Thread 1168681312 (LWP 29079)] [New Thread 1157925216 (LWP 28716)] [New Thread 1147435360 (LWP 28657)] [New Thread 1147169120 (LWP 28656)] [New Thread 1136679264 (LWP 28497)] [New Thread 1126189408 (LWP 28496)] [New Thread 1115699552 (LWP 28495)] [New Thread 1105209696 (LWP 28494)] [New Thread 1094719840 (LWP 28491)] [New Thread 1084229984 (LWP 28490)] 0x0000003f83e0bf99 in waitpid () from /lib64/libpthread.so.0
+ Trace 61455
Thread 1 (Thread 46912496356672 (LWP 28474))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-23 15:37 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was gavin@planetacetech.com.
Gavin: This looks like when replying to a message Evolution crashed. If possible can you please attach the email source with this bug ?
I no longer know what e-mail it was. The crashes were never repeatable so I didn't think to note that information. I've been running the 32-bit version of FC4 for the past few days and since that change haven't seen an evolution crash. I'll try switching back to the 64-bit version and see if I can get another stack trace and better information as to what I was doing when it crashes.
I can now reproduce the crash, but only when running an smp x86_64 kernel (i.e. I cannot reproduce in 32-bit mode at all, or in non-smp 64-bit mode). To "reproduce", just hit Reply to any e-mail, close the resulting message dialog, and repeat. On my system it segfaults after 2 - 10 times of this. Here is some gdb output: Program received signal SIGSEGV, Segmentation fault.
+ Trace 61772
Thread 8 (Thread 1136679264 (LWP 4237))
Thread 1 (Thread 46912502362368 (LWP 4222))
Info supplied: reopening it, changing summary to reflect the problem.
looks like a problem in enameselector do you get any warnings before it fails?
*** This bug has been marked as a duplicate of 274204 ***
Not Zed: there are no messages printed on the console. I get the following, but the last message "BBDB spinning up..." was printed well before the crash. [gavin@boll ~]$ evolution es menu class init adding hook target 'source' (evolution:6238): evolution-mail-WARNING **: couldn't get service : No provider available for protocol `' update flow align BBDB spinning up...