Bug 883609

Summary: [abrt] evolution-data-server-3.6.2-2.fc18: g_malloc0: Process /usr/libexec/evolution-addressbook-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Štefan Gurský <scorpy_sk>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: gergely, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:10e1159ca9dafb76dd4db5abc4bdfdf61c5aae12
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 13:34:04 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: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: smolt_data none

Description Štefan Gurský 2012-12-05 00:34:49 UTC 
Version-Release number of selected component:
evolution-data-server-3.6.2-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-addressbook-factory
crash_function: g_malloc0
executable:     /usr/libexec/evolution-addressbook-factory
kernel:         3.6.7-5.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000
var_log_messages: Dec  5 01:16:57 napo abrt[8726]: Saved core dump of pid 1372 (/usr/libexec/evolution-addressbook-factory) to /var/spool/abrt/ccpp-2012-12-05-01:16:55-1372 (408506368 bytes)

Truncated backtrace:
Thread no. 1 (9 frames)
 #3 g_malloc0 at gmem.c:189
 #4 thread_memory_from_self at gslice.c:512
 #6 g_slice_free1 at gslice.c:1087
 #7 g_list_free_1 at glist.c:166
 #8 g_queue_pop_tail at gqueue.c:632
 #9 g_async_queue_pop_intern_unlocked at gasyncqueue.c:431
 #10 g_async_queue_timeout_pop_unlocked at gasyncqueue.c:572
 #11 g_thread_pool_wait_for_new_task at gthreadpool.c:264
 #13 g_thread_proxy at gthread.c:797
Comment 1 Štefan Gurský 2012-12-05 00:34:52 UTC 
Created attachment 657830 [details]
File: backtrace
Comment 2 Štefan Gurský 2012-12-05 00:34:55 UTC 
Created attachment 657831 [details]
File: build_ids
Comment 3 Štefan Gurský 2012-12-05 00:34:57 UTC 
Created attachment 657832 [details]
File: cgroup
Comment 4 Štefan Gurský 2012-12-05 00:34:59 UTC 
Created attachment 657833 [details]
File: core_backtrace
Comment 5 Štefan Gurský 2012-12-05 00:35:01 UTC 
Created attachment 657834 [details]
File: dso_list
Comment 6 Štefan Gurský 2012-12-05 00:35:03 UTC 
Created attachment 657835 [details]
File: environ
Comment 7 Štefan Gurský 2012-12-05 00:35:05 UTC 
Created attachment 657836 [details]
File: limits
Comment 8 Štefan Gurský 2012-12-05 00:35:07 UTC 
Created attachment 657837 [details]
File: maps
Comment 9 Štefan Gurský 2012-12-05 00:35:10 UTC 
Created attachment 657838 [details]
File: open_fds
Comment 10 Štefan Gurský 2012-12-05 00:35:11 UTC 
Created attachment 657839 [details]
File: proc_pid_status
Comment 11 Štefan Gurský 2012-12-05 00:35:13 UTC 
Created attachment 657840 [details]
File: smolt_data
Comment 12 Milan Crha 2012-12-05 08:17:50 UTC 
Thanks for a bug report. It seems to me, if I read the backtrace right, that this happened at the end of one thread pool task, with basically no other action in the factory (all other threads look like idle, except of Thread 7, which is stopping a view). A crash in malloc_consolidate() usually means a memory corruption, but I cannot say from the backtrace for sure. Hence my question:
is this reproducible on your side after certain steps, probably in Evolution itself, or was this just a one-time, occasional crash?
Comment 13 Fedora End Of Life 2013-12-21 09:38:32 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 14 Fedora End Of Life 2014-02-05 13:34:07 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 15 Štefan Gurský 2014-06-23 11:19:34 UTC 
Junk comment just to remove needinfo and stop bugzilla from spamming me. I do not remember that crash anymore and do not remember evolution crashing without known reason in some time.