Version-Release number of selected component: evolution-3.4.4-2.fc17 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 backtrace_rating: 4 cmdline: evolution crash_function: toggle_refs_notify kernel: 3.5.4-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (4 frames) : #0 toggle_refs_notify at gobject.c:2720 : #1 refresh_folders_exec at mail-send-recv.c:1056 : #2 mail_msg_proxy at mail-mt.c:423 : #4 g_thread_proxy at gthread.c:801
Created attachment 619931 [details] File: core_backtrace
Created attachment 619932 [details] File: environ
Created attachment 619933 [details] File: limits
Created attachment 619934 [details] File: backtrace
Created attachment 619935 [details] File: cgroup
Created attachment 619936 [details] File: maps
Created attachment 619937 [details] File: dso_list
Created attachment 619938 [details] File: var_log_messages
Created attachment 619939 [details] File: open_fds
Thanks for a bug report. I do not see anything useful from the backtrace, it seems to me like some ref-counting error, probably during Send/Receive operation, but that's the most I can read from the backtrace. Is this just an occasional crash, or you got this repeatedly/multiple times? Some steps for a reproducer would help to identify the issue for sure.
Hi Milan, I am having a few Evolution crashes per week. I am still trying to find out the cause of these crashes. (they may even have multiple causes) So I don't have a nice "how to reproduce"-description (yet). If you think that this bug is useless without that, please feel free to close it. kind regards, Egon
Thanks for the update. I would try to run evolution under valgrind, but it's significantly slower that usually, due to all the memory checking. And on Fedora 17 is better to suppress the wcslen valgrind "errors", because it's used too often. I can guide you what to do, if you would give it a try (maybe like left running evolution under valgrind over night, when the automatic account refresh will be invoked multiple times).
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 17'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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.