| Summary: | [abrt] evolution-3.0.2-1.fc15: __libc_free: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Braden McDaniel <braden> | ||||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 15 | CC: | lucilanga, mbarnes, mcrha | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:ce8c4a4e85fa951ec26751f7ef5ba6e94e352703 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-08-07 17:04:52 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Braden McDaniel
2011-06-06 05:22:20 UTC
Created attachment 503146 [details]
File: dsos
Created attachment 503147 [details]
File: maps
Created attachment 503148 [details]
File: backtrace
Thanks for a bug report. This is similar to bug #707578, but not exactly the same. Could you give a try to evolution-3.0.2-2 from updates testing, which is fixing the issue I introduced in 3.0.2-1, whether it'll help here too, please? Thanks in advance. I've encountered the same crash using 3.0.2-2. Thanks for a quick update. In that case it will be slightly different issue, probably accessing already freed memory. Could you run evolution under valgrind and try to reproduce it, please? The thing is that evolution will be significantly slower due to all the memory checking done by valgrind, but maybe this will show us where the memory got freed. You can run evolution under valgrind like this: $ G_SLICE=always-malloc valgrind evolution &>log.txt then try to use evolution for some time (it'll be really slow), and then close evolution. The resulting log.txt may discover some issues, hopefully. Also note that the evolution may not crash always, valgrind can avoid certain types of crashes, but will report them to the log. I will try that. Meanwhile, I think I know a series of steps that will reliably produce this crash. 1. Misconfigure the SMTP server configuration such that sending mail will fail. 2. Have mail waiting to be sent in the Outbox. 3. Do Send/Receive mail. 4. After 15-30 seconds, cancel the Send/Receive mail operation. 5. At this point, you should get a red error notification before the Send/Receive dialog goes away. Dismiss it. Pity, I tried to reproduce this with no luck. I see all but the crash when trying your steps from comment #7. This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |