Bug 1075096

Summary: [abrt] evolution-data-server: g_malloc0(): evolution-addressbook-factory killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Jerry James <loganjerry>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fabiano, loganjerry, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a2552eb3f5800341349aad2cb6ce84d11085199d
Whiteboard: abrt_hash:c6077736b272e2f2608f5eadc1d0cd77e99d229a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-14 07:51:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jerry James 2014-03-11 13:48:43 UTC 
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
Comment 1 Jerry James 2014-03-11 13:48:47 UTC 
Created attachment 873136 [details]
File: backtrace
Comment 2 Jerry James 2014-03-11 13:48:51 UTC 
Created attachment 873137 [details]
File: cgroup
Comment 3 Jerry James 2014-03-11 13:48:53 UTC 
Created attachment 873138 [details]
File: core_backtrace
Comment 4 Jerry James 2014-03-11 13:48:57 UTC 
Created attachment 873139 [details]
File: dso_list
Comment 5 Jerry James 2014-03-11 13:49:01 UTC 
Created attachment 873140 [details]
File: environ
Comment 6 Jerry James 2014-03-11 13:49:03 UTC 
Created attachment 873141 [details]
File: exploitable
Comment 7 Jerry James 2014-03-11 13:49:05 UTC 
Created attachment 873142 [details]
File: limits
Comment 8 Jerry James 2014-03-11 13:49:06 UTC 
Created attachment 873143 [details]
File: maps
Comment 9 Jerry James 2014-03-11 13:49:10 UTC 
Created attachment 873144 [details]
File: open_fds
Comment 10 Jerry James 2014-03-11 13:49:20 UTC 
Created attachment 873145 [details]
File: proc_pid_status
Comment 11 Jerry James 2014-03-11 13:49:21 UTC 
Created attachment 873146 [details]
File: var_log_messages
Comment 12 Milan Crha 2014-03-13 10:11:34 UTC 
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
Comment 13 Jerry James 2014-03-13 15:22:47 UTC 
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. :-(
Comment 14 Milan Crha 2014-03-14 07:51:35 UTC 
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.