Version-Release number of selected component: evolution-data-server-3.10.4-2.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.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #3 g_malloc0 at gmem.c:134 #4 thread_memory_from_self at gslice.c:525 #6 g_slice_alloc at gslice.c:994 #7 g_variant_builder_new at gvariant.c:3213 #8 e_gdbus_signal_emission_hook_uint_string at e-gdbus-templates.c:240 #12 e_gdbus_book_view_emit_progress at e-gdbus-book-view.c:315 #13 e_data_book_view_notify_progress at e-data-book-view.c:1113 #14 book_view_thread at e-book-backend-file.c:883 #15 g_thread_proxy at gthread.c:798
Created attachment 873136 [details] File: backtrace
Created attachment 873137 [details] File: cgroup
Created attachment 873138 [details] File: core_backtrace
Created attachment 873139 [details] File: dso_list
Created attachment 873140 [details] File: environ
Created attachment 873141 [details] File: exploitable
Created attachment 873142 [details] File: limits
Created attachment 873143 [details] File: maps
Created attachment 873144 [details] File: open_fds
Created attachment 873145 [details] File: proc_pid_status
Created attachment 873146 [details] File: var_log_messages
Thanks for a bug report. I'd say from a backtrace that there happened something with the memory, like a memory corruption (when something wrote to an already freed memory or some such kind of issue), which can be similar to an upstream bug [1], but I'm not completely sure of it. There would help if you've any steps for a reproducer, do you have any clue, please? [1] https://bugzilla.gnome.org/show_bug.cgi?id=724217
Alas, no. I wasn't even using evolution at the time, so I don't know what happened to trigger this bug. I'm afraid that I have no idea how to reproduce the crash. :-(
Thanks for the update. It's not easy to reproduce this kind of bugs, especially when the actual memory corruption can strike each time in a different place, in a different time. Let's deal with this within the upstream bug report.