GNOME Bugzilla – Bug 383389
Accessing Global Address List causes crash - sometimes
Last modified: 2007-03-01 18:42:54 UTC
Steps to reproduce: Evolution version: 2.8.2.1 on FC6 I believe this is caused by accessing the global address list for the autocomplete feature at the same time that a new message arrives. It has crashed in the autocomplete area for me several times before, but I didn't have any other information to give until now. This is the second time its crashed while doing an autocomplete lookup and a new message arrives. Please note that I have not reliably reproduced this yet due to the odd times that it happens. 1. Start up evolution and have it running for a while (it doesn't do this once I've restarted it after the crash) 2. open a new message and begin typing an address or two. 3. if a new message arrives when the autocomplete feature is doing its thing, this crash may happen. Like I said before, this has been going on for a while, but I've been trying to get more details of reliably reproducing the crash - to no avail :( Stack trace: System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 85884928 vsize: 0 resident: 85884928 share: 0 rss: 28270592 rss_rlim: 0 CPU usage: start_time: 1165418353 rtime: 0 utime: 4735 stime: 0 cutime:3933 cstime: 0 timeout: 802 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-exchange' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208170272 (LWP 24787)] [New Thread -1221031024 (LWP 658)] [New Thread -1210270832 (LWP 24789)] 0x00e3f402 in __kernel_vsyscall ()
+ Trace 92323
Thread 2 (Thread -1221031024 (LWP 658))
Other information:
Ok, I'm revising this to say I don't know whether or not the receiving of email has anything to do with the crash. Evo-exch-stor just crashed on me twice today when I was typing in the To: field (autocomplete), and no new mail arrived. Below is the stack trace from the most recent crash: System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 92434432 vsize: 0 resident: 92434432 share: 0 rss: 35954688 rss_rlim: 0 CPU usage: start_time: 1165514907 rtime: 0 utime: 5902 stime: 0 cutime:4882 cstime: 0 timeout: 1020 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-exchange' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208973088 (LWP 2748)] [New Thread -1265636464 (LWP 15375)] [New Thread -1211073648 (LWP 2749)] 0x00c77402 in __kernel_vsyscall ()
+ Trace 92642
Thread 2 (Thread -1265636464 (LWP 15375))
Created attachment 81207 [details] Bug Buddy generated when the crash happened
This happens to me frequently. Although the problem appears random, it seems that the faster I type the name in the address line, the more likely the problem is to occur. Obviously this is a subjective metric. Attachement on comment #2 is the Bug Buddy report which was generated during my last crash.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 332979 ***