Red Hat Bugzilla – Bug 809458
[abrt] evolution-3.2.3-2.fc16: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Last modified: 2013-02-13 11:41:03 EST
libreport version: 2.0.8
comment: I don't know what triggered the crash. Evolution is regularly crashing for me now, frequently within a few seconds after it is first started / executed. This time I was in the middle of composing a message.
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
time: Tue 03 Apr 2012 01:15:36 PM BST
var_log_messages: Apr 3 13:15:38 jack-laptop abrt: Saved core dump of pid 10775 (/usr/bin/evolution) to /var/spool/abrt/ccpp-2012-04-03-13:15:36-10775 (184991744 bytes)
backtrace: Text file, 90696 bytes
build_ids: Text file, 7708 bytes
dso_list: Text file, 18535 bytes
maps: Text file, 56069 bytes
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
Created attachment 574846 [details]
Created attachment 574847 [details]
Created attachment 574848 [details]
Created attachment 574849 [details]
Thanks for a bug report. I see from the backtrace that there happened a memory corruption, two threads are allocating memory, but it fails in a memory checker. I also see that you use IMAP+, thus I guess it's related to it. There had been done "few" changes in its code recently, also addressing possible memory corruptions, which are part of 3.4.0, which will be part of upcoming Fedora 17.
As a workaround, I would try to switch from IMAP+ to IMAP in your accounts (such change requires evolution's restart), and if it'll still crash for you, then run evolution under valgrind, please, it'll hopefully show us where the memory got corrupted. Note the evolution will be significantly slower, due to all memory checking. The valgrind command looks like this:
$ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt
Valgrind can sometimes avoid certain crashes, thus the log can contain the information, even if the evolution will not crash. I see that this happened for you when was evolution updating folders, checking for changes on the server side.
> As a workaround, I would try to switch from IMAP+ to IMAP in your accounts
(such change requires evolution's restart), and if it'll still crash for you,
then run evolution under valgrind, please, it'll hopefully show us where the
memory got corrupted. Note the evolution will be significantly slower, due to
all memory checking.
Will do, thanks for detailed info!
(In reply to comment #6)
> Will do, thanks for detailed info!
Thanks. I'm setting this back to need-info, because the actual information whether the change helped, and/or the valgrind log, is still pending here.
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.
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 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 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 to click on
"Clone This Bug" and open it against that version of Fedora.
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.
The process we are following is described here:
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.
Thank you for reporting this bug and we are sorry it could not be fixed.