GNOME Bugzilla – Bug 501295
crash in e_file_cache_get_object at e-file-cache.c:318?
Last modified: 2008-08-27 03:24:32 UTC
What were you doing when the application crashed? replying to an email Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.16-2-686 #1 Fri Aug 18 19:01:49 UTC 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 73879552 vsize: 73879552 resident: 23334912 share: 10342400 rss: 23334912 rss_rlim: 4294967295 CPU usage: start_time: 1196697184 rtime: 2847 utime: 2673 stime: 174 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xa65ea6b0 (LWP 17852)] [New Thread 0xa3afeb90 (LWP 24096)] [New Thread 0xa6544b90 (LWP 17854)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 180587
Thread 2 (Thread 0xa3afeb90 (LWP 24096))
----------- .xsession-errors (942 sec old) --------------------- WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) suspended. Weaver dtor: destroying inventory. WeaverThreadLogger: thread (ID: 1) destroyed. WeaverThreadLogger: thread (ID: 2) destroyed. WeaverThreadLogger: thread (ID: 3) destroyed. WeaverThreadLogger: thread (ID: 4) destroyed. Weaver dtor: done DCOP Cleaning up dead connections. ICE default IO error handler doing an exit(), pid = 21942, errno = 0 (evolution:17789): libebook-WARNING **: EBookView: Exception while releasing BookView BBDB spinning up... --------------------------------------------------
Thanks for that awesome stacktrace. Looks unique. Is this bug perfectly reproduceable for you?
If you mean, does it happen often, the answer is daily, or more often. If you mean, is it the same problem crash, then I don't know. I have to kill and restart Evolution at least 3-5 times per day because it crashes so much. Does not happen with Evolution alone, just the Evolution/Exchange combo.
I'm sorry that it crashes so often for you. Are you doing anything special like add/removing/changing contacts or answering a mail? Could you attach a gdb to the process and get us a trace as described in http://live.gnome.org/GettingTraces/Details ? What version of Exchange are you using? Do you have any special mails or contacts like subjects (or names) with special characters?
No special characters...just plain old English text. I use a third party Exchange service - mailstreet.com. I am using the version of Exchange that is recommended by my version of Evolution. It is not the latest version of Exchange, and I had to have my account downgraded to the version I am using. But the docs for the Exchange connector specifies the version of Exchange, and that is the version I am using. I have gdb running and will attach the trace when it crashes. BTW, I attached gdb to the "evolution" process. There are other evolution processes - which one do you want? mark@narwhale:~$ ps aux | grep evolution mark 18678 0.0 0.6 33380 6388 ? Sl 09:27 0:00 /usr/lib/evolution/evolution-data-server-1.12 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_InterfaceCheck --oaf-ior-fd=28 mark 18695 0.2 2.1 96152 22172 ? Sl 09:27 0:06 /usr/lib/evolution/2.10/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Component_Factory:2.10 --oaf-ior-fd=29 mark 18711 0.0 0.9 67744 10216 ? Sl 09:27 0:00 /usr/lib/evolution/2.10/evolution-alarm-notify --oaf-activate-iid=OAFIID:GNOME_Evolution_Calendar_AlarmNotify_Factory:2.10 --oaf-ior-fd=30 mark 20888 0.5 8.4 90664 87256 pts/2 S+ 10:01 0:02 gdb /usr/bin/evolution 18619 mark 18619 0.6 3.7 169428 38556 ? Sl 09:27 0:17 /usr/bin/evolution mark 21395 0.0 0.0 2100 652 pts/3 S+ 10:09 0:00 grep evolution mark@narwhale:~$
*** Bug 501552 has been marked as a duplicate of this bug. ***
Good question actually. I'm not sure, but as it's an exchange related crasher, you might want to try /usr/lib/evolution/2.10/evolution-exchange-storage
*** Bug 503142 has been marked as a duplicate of this bug. ***
*** Bug 503046 has been marked as a duplicate of this bug. ***
*** Bug 502972 has been marked as a duplicate of this bug. ***
*** Bug 503647 has been marked as a duplicate of this bug. ***
Created attachment 102617 [details] [review] Proposed patch
Looks like some thread synchronization issue. The cache seems to be corrupted. This locking might help. If any one can try this patch, it might be great.
*** Bug 386022 has been marked as a duplicate of this bug. ***
srini, if there's no potential harm by applying this, i'd tend to commit this to svn, close as fixed, and ask for reopen if we get a duplicate from >=2.21.91.
Andre, I was thinking the same, but wanted to try and since the libsoup issues I'm not able to test it myself. Just fixed the libsoup issue, I think I will test this myself and commit it.
Committed to trunk a slightly modified version (found a bug myself when tested it) Please reopen if any bugs found later to 2.21.91.
*** Bug 460617 has been marked as a duplicate of this bug. ***