Version-Release number of selected component: evolution-data-server-3.10.3-1.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory crash_function: g_malloc0 executable: /usr/libexec/evolution-addressbook-factory kernel: 3.12.9-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #6 g_malloc0 at gmem.c:134 #7 e_sexp_add_function at e-sexp.c:1571 #8 e_sexp_init at e-sexp.c:1513 #9 e_sexp_new at e-sexp.c:1533 #10 e_book_backend_sexp_new at e-book-backend-sexp.c:1142 #11 book_backend_google_get_contact_list_sync at e-book-backend-google.c:2105 #12 book_backend_get_contact_list_thread at e-book-backend.c:2403 #13 book_backend_dispatch_thread at e-book-backend.c:187 #14 io_job_thread at gioscheduler.c:89 #15 g_task_thread_pool_thread at gtask.c:1245
Created attachment 861999 [details] File: backtrace
Created attachment 862000 [details] File: cgroup
Created attachment 862001 [details] File: core_backtrace
Created attachment 862002 [details] File: dso_list
Created attachment 862003 [details] File: environ
Created attachment 862004 [details] File: limits
Created attachment 862005 [details] File: maps
Created attachment 862006 [details] File: open_fds
Created attachment 862007 [details] File: proc_pid_status
Created attachment 862008 [details] File: var_log_messages
Thanks for a bug report. I see from the backtrace that this crashed during a search in a Google's address book, the 'malloc' function detected a memory corruption, which is a fault of the application, and/or some library it uses, sometimes caused by use-after-free of some structure. I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions. [1] https://bugzilla.gnome.org/show_bug.cgi?id=724217
*** Bug 1064313 has been marked as a duplicate of this bug. ***
*** Bug 1065621 has been marked as a duplicate of this bug. ***