Red Hat Bugzilla – Bug 965581
[abrt] claws-mail-3.9.0-1.fc18: allocator_memalign: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Last modified: 2014-01-20 06:32:03 EST
Version-Release number of selected component:
Thread no. 1 (10 frames)
#4 allocator_memalign at gslice.c:1381
#5 allocator_add_slab at gslice.c:1252
#6 slab_allocator_alloc_chunk at gslice.c:1300
#7 magazine_cache_pop_magazine at gslice.c:724
#8 thread_memory_magazine1_reload at gslice.c:794
#9 g_slice_alloc at gslice.c:992
#10 g_slice_alloc0 at gslice.c:1029
#11 g_type_create_instance at gtype.c:1870
#12 g_object_constructor at gobject.c:1854
#15 gtk_image_new at gtkimage.c:1523
Created attachment 751062 [details]
Created attachment 751063 [details]
Created attachment 751064 [details]
Created attachment 751065 [details]
Created attachment 751066 [details]
Created attachment 751067 [details]
Created attachment 751068 [details]
Created attachment 751069 [details]
Created attachment 751070 [details]
Created attachment 751071 [details]
Is it reproducible? Perhaps you remember what you've been doing when you see the mail's subject mentioned in the backtrace.
Crashes in memory management (and taking down the GTK+ UI) can be due to anything ranging from unstable hardware to memory corruption.
#36 0x080bd3b9 in compose_generic_new (account=0x916b788, account@entry=0x0, mailto=0xbfea4130 "mailto:email@example.com?subject=PHP-%D1%80%D0%B0%D0%B7%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D1%87%D0%B8%D0%BA%D0%B8%20%28Yii%29%20-%20%D0%B2%D0%B0%D0%BA%D0%B0%D0%BD%D1%81%D0%B8%D1%8F%20%D1%81%20%D0%A5%D0%B0"..., mailto@entry=0x0, item=item@entry=0x0, attach_files=0x0, listAddress=0x0) at compose.c:1000
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.
We really need a bit of background in addition to backtraces, or else our hands are tied. Upstream also would want to know how to reproduce a problem or whether it is only a sporadic crash and a side-effect.