Red Hat Bugzilla – Bug 1031969
[abrt] evolution-3.10.2-1.fc20: allocator_memalign: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Last modified: 2015-06-29 08:59:55 EDT
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#5 allocator_memalign at gslice.c:1394
#6 allocator_add_slab at gslice.c:1265
#7 slab_allocator_alloc_chunk at gslice.c:1313
#8 magazine_cache_pop_magazine at gslice.c:737
#9 thread_memory_magazine1_reload at gslice.c:807
#10 g_slice_alloc at gslice.c:1005
#11 g_slice_alloc0 at gslice.c:1042
#12 g_type_create_instance at gtype.c:1850
#13 g_object_new_internal at gobject.c:1746
#16 camel_mime_message_new at camel-mime-message.c:408
Potential duplicate: bug 833228
Created attachment 825969 [details]
Created attachment 825970 [details]
Created attachment 825971 [details]
Created attachment 825972 [details]
Created attachment 825973 [details]
Created attachment 825974 [details]
Created attachment 825975 [details]
Created attachment 825976 [details]
Created attachment 825977 [details]
Created attachment 825978 [details]
Created attachment 825979 [details]
Thanks for a bug report. The cause of this is basically the same as yours bug #1031637, but this time in evolution process, instead of evolution-source-registry process. There happened some (software) memory corruption in the process. Weird you've got it in two different processes.
I seem to have been hit by this also.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version'
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.
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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
Thank you for reporting this bug and we are sorry it could not be fixed.