Description of problem: while updating a contact Version-Release number of selected component: evolution-data-server-3.10.4-3.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory crash_function: magazine_cache_trim executable: /usr/libexec/evolution-addressbook-factory kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #2 magazine_cache_trim at gslice.c:685 #3 magazine_cache_push_magazine at gslice.c:716 #4 thread_memory_magazine2_unload at gslice.c:815 #5 g_slice_free_chain_with_offset at gslice.c:1186 #6 g_list_free at glist.c:152 #7 g_list_free_full at glist.c:188 #8 vcard_finalize at e-vcard.c:164 #10 e_book_backend_modify_contacts_finish at e-book-backend.c:1805 #11 data_book_complete_modify_contacts_cb at e-data-book.c:881 #12 g_simple_async_result_complete at gsimpleasyncresult.c:777
Created attachment 880969 [details] File: backtrace
Created attachment 880972 [details] File: cgroup
Created attachment 880973 [details] File: core_backtrace
Created attachment 880975 [details] File: dso_list
Created attachment 880976 [details] File: environ
Created attachment 880977 [details] File: exploitable
Created attachment 880978 [details] File: limits
Created attachment 880979 [details] File: maps
Created attachment 880980 [details] File: open_fds
Created attachment 880981 [details] File: proc_pid_status
Created attachment 880982 [details] File: var_log_messages
Thanks for a bug report. I see from the backtrace that this crashed after the modification of a contact had been over, when freeing the actual object. It seems like some part of the code already freed the memory which was about to be freed. Could you provide some more information, please? It would help to identify the issue, when you'll answer the following questions: a) what was the addressbook type where the change of the contact was made? (On This Computer, On The Web, LDAP, ....) b) do you remember what exact change was made to the contact, please? It can be that certain changes don't exhibit the issue. Thanks in advance.
I can confirm the record was actually changed. It was Google's addressbook. I was adding a postal address to an existing contact. The contact probably had Google+ account (I could see their avatar on my Android, and I hadn't added it manually) if this matters. The issue is not reproducible.
Thanks for the update. The symptoms are basically the same as in an upstream bug report [1], thus I'm closing this in a favour of it. Please see it for any further changes. My personal opinion is that some change in the contact causes memory corruption (like if a process writes to an already freed memory, or some memory is freed twice, or ...), which can exhibit in many ways. As the symptoms of "updating a contact in a Google book" are the same, I'd say this is the same issue. The clue of changing particular field is helpful. [1] https://bugzilla.gnome.org/show_bug.cgi?id=725045