Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Version-Release number of selected component:
evolution-data-server-3.6.0-1.0.MCbgo268618.2.el7

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-addressbook-factory
crash_function: g_slice_alloc
kernel:         3.6.0-0.28.el7.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 g_slice_alloc at /lib64/libglib-2.0.so.0
: #1 g_bytes_new_with_free_func at /lib64/libglib-2.0.so.0
: #2 g_variant_new_from_trusted at /lib64/libglib-2.0.so.0
: #3 g_variant_new_byte at /lib64/libglib-2.0.so.0
: #4 parse_value_from_blob at /lib64/libgio-2.0.so.0
: #7 g_dbus_message_new_from_blob at /lib64/libgio-2.0.so.0
: #8 _g_dbus_worker_do_read_cb at /lib64/libgio-2.0.so.0
: #9 g_simple_async_result_complete at /lib64/libgio-2.0.so.0
: #10 complete_in_idle_cb at /lib64/libgio-2.0.so.0
: #12 g_main_context_iterate.isra.24 at /lib64/libglib-2.0.so.0

Created attachment 642252 [details]
File: core_backtrace

Created attachment 642253 [details]
File: environ

Created attachment 642254 [details]
File: backtrace

Created attachment 642255 [details]
File: limits

Created attachment 642256 [details]
File: cgroup

Created attachment 642257 [details]
File: executable

Created attachment 642258 [details]
File: maps

Created attachment 642259 [details]
File: dso_list

Created attachment 642260 [details]
File: build_ids

Created attachment 642261 [details]
File: var_log_messages

Created attachment 642262 [details]
File: open_fds

Created attachment 642263 [details]
File: proc_pid_status

It looks like a memory corruption to me Would you mind to retest with 3.8.5, please? The things could change between 3.6.0 and 3.8.5. Please reopen, if you see this with 3.8.5+. Thanks in advance.