GNOME Bugzilla – Bug 638821
Abort in e-addressbook-factory due to freed backend
Last modified: 2011-09-23 07:42:36 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=667110 abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/e-addressbook-factory component: evolution-data-server crash_function: talloc_abort executable: /usr/libexec/e-addressbook-factory kernel: 2.6.35.10-74.fc14.x86_64 package: evolution-data-server-2.32.1-1.fc14 rating: 4 reason: Process /usr/libexec/e-addressbook-factory was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1294148423 uid: 500 How to reproduce ----- 1. Just sent an email when the crash occurred. Core was generated by `/usr/libexec/e-addressbook-factory'. Program terminated with signal 6, Aborted.
+ Trace 225435
Thread 1 (Thread 2695)
Same issue from 3.0.2: https://bugzilla.redhat.com/show_bug.cgi?id=716418
*** Bug 655316 has been marked as a duplicate of this bug. ***
Created attachment 193321 [details] [review] ema patch for evolution-mapi; This, together with a fix from an OpenChange issue [1], fixes the problem for me. My reproducer steps were pretty simple, though it requires OpenChange 0.11 for me: a) close all evolution-related processes b) run e-addressbook-factory under valgrind (not because getting it slow, but to have show issues, if any) c) run evolution; make sure at least two books from MAPI are set for autocompletion d) invoke a new message composer and autocomplete there, but do not wait too long - for me was enough when the local addressbook returned a result for the completion query e) close composer window All these steps may result in a backend removal from the factory, thus also for a Logoff() call. The main thing was that the backend gone before it finished its waiting for connection, thus anything later was done on an already freed object. See [1] for details of an issue on OpenChange 0.11 side. [1] http://tracker.openchange.org/issues/366
Created commit 84b5100 in ema master (3.1.5+) Created commit 2b71f90 in ema gnome-3-0 (3.0.3+)
*** Bug 655314 has been marked as a duplicate of this bug. ***
*** Bug 655930 has been marked as a duplicate of this bug. ***
*** Bug 655932 has been marked as a duplicate of this bug. ***
I'm still having this crash when working with Exchange 2007. []$ rpm -qa |grep evolution evolution-NetworkManager-3.0.3-1.fc15.x86_64 evolution-3.0.3-1.fc15.x86_64 evolution-mapi-3.0.3-2.fc15.x86_64 evolution-data-server-3.0.3-1.fc15.x86_64 Abrt is trying to report this crash as bug 719841.
Hrm, then it might mean either I didn't spot all cases with the fix or the issue is slightly different with openchange 0.9. How do your steps differ from that mine from comment #3, please?
The most popular crash is when I have two composer windows opened, enter e-mail in first window, then EDS dies immediatelly after autocompletion e-mail address in second composer window.
Hrm, I tried to reproduce this with 3.1.92 and no luck. What I do: a) open a new composer window A b) open a new composer window B c) autocomplete in B a contact from evo-mapi addressbook d) switch to A and autocomplete the same contact from evo-mapi addressbook e) close A and B composers (order doesn't matter) I also see the e-addressbook-factory being correctly closed when no longer needed (after I closed both composer windows)
Seems, that I have to install virtual F16 alpha, make mass upgrade, and try it. From my local notebook, I have to stick with F15 packages.... as stable ones ;)