GNOME Bugzilla – Bug 691526
[abrt] Memory corruption under e_book_backend_google_start_book_view()
Last modified: 2013-07-18 16:34:51 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=894208 Version-Release number of selected component: evolution-data-server-3.6.2-3.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory crash_function: slab_allocator_alloc_chunk executable: /usr/libexec/evolution-addressbook-factory kernel: 3.6.10-4.fc18.i686 Core was generated by `/usr/libexec/evolution-addressbook-factory'. Program terminated with signal 11, Segmentation fault.
+ Trace 231370
Thread 2 (Thread 0xb77c7740 (LWP 1648))
stream bug report about the same from 3.8.3: https://bugzilla.redhat.com/show_bug.cgi?id=985552 Other threads are also busy with memory allocation and the same backend's processing start_view for other views.
+ Trace 232263
Thread 1 (Thread 0xaa8fdb40 (LWP 20504))
Created attachment 249544 [details] [review] eds patch for evolution-data-server; I cannot reproduce this myself, but it seems to me that the issue is that multiple threads are in start_view and also multiple threads are updating the local cache, which is not thread safe, thus a "proper" thread interleaving can cause such damage. Thus a logic step is to add locking around the local cache object, when the backend reads or writes data from/to it.
Created commit 9dd16ed in eds master (3.9.5+) Created commit 9b33d90 in eds gnome-3-8 (3.8.4+)