| Summary: | [abrt] evolution-3.2.3-1.fc16: Process /usr/bin/evolution was killed by signal 6 (SIGABRT) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> | ||||||||||||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||
| Version: | 16 | CC: | johnmargaritopoulos, lucilanga, mbarnes, mcrha, sanchezhiguera | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | i686 | ||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||
| Whiteboard: | abrt_hash:4798e2c95f45bf691dd58a839a65e514fdda8686 | ||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2013-02-13 16:39:32 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
Mikhail
2012-01-30 04:25:04 UTC
Created attachment 558256 [details]
File: dso_list
Created attachment 558257 [details]
File: gconf_subtree
Created attachment 558258 [details]
File: maps
Created attachment 558259 [details]
File: backtrace
Thanks for a bug report. I see in the backtrace that multiple threads reported issues with memory, caused by severe memory corruption. The question is where and why the memory corruption happened. I recall one place, which can cause things like this. It is tracker-evolution-plugin. Do you have this installed, please? Maybe if you disable or uninstall it, then this will be solved. If this is caused by something else, then I'm not aware of any other method than running evolution under valgrind, to let it check the memory operations being done and report any errors it may found. The issue with valgrind is that the process is significantly slower due to all memory checking. The command looks like this: $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt Note that valgrind can avoid certain crashes, it logs about them instead, thus even if the application will not crash then the log can contain the information about the issue. Also make sure that you've installed correct debug information packages at least for gtkhtml3, evolution-data-server, evolution and any other evolution-* packages you are using, thus the log will contained detailed debug information. With 'correct' is meant that the binary package version should be the same as the debuginfo package version, otherwise the symbols doesn't match. *** Bug 785630 has been marked as a duplicate of this bug. *** Created attachment 558528 [details]
valgrind log
Thanks for the update. Did evolution crash under valgrind too? The log is missing some footer valgrind usually prints, but it also doesn't show the crash itself. The interesting part, from my point of view, is that your MAPI account cannot connect to your server, with an error: NT_STATUS_CONNECTION_REFUSED. Apart of that the log doesn't show any unusal issues from libraries evolution is using, which makes this harder to resolve. Created attachment 559046 [details]
yet another valgrind log
Please see yet another valgrind log. Created attachment 559203 [details]
yet another valgrind log 2
Thanks for the update. I'm afraid this cannot be catch by valgrind, neither of those two show any issue I would expect. The second one is quite impressive, because it leaked more than 150MB of memory in not so many blocks. What was the machine doing, just updating? You can add beside --num-callers=50 also parameter --leak-check=full, where the log will contain all such information (the log will be significantly larger). Like I mentioned in comment #5, without debug info packages for evolution-related packages the logs will not be fully usable. Did you try to disable or uninstall the tracker plugin? You can check when you run evolution from console, it may not mentions Tracker there at all. The valgrind logs you sent above don't have it there mentioned, thus you have it gone probably. ==6101== LEAK SUMMARY: ==6101== definitely lost: 172,293,627 bytes in 16,831 blocks Backtrace analysis of bugs across components suggests the actual bug might be in component glib2 instead of component evolution. You might want to inspect the backtraces from the bugs listed below to find out the correct component. Bugs which were found to be similar to this bug: nautilus: bug #758517 rhythmbox: bug #761611, bug #761612, bug #761613 This comment is automatically generated. *** Bug 758517 has been marked as a duplicate of this bug. *** *** Bug 761613 has been marked as a duplicate of this bug. *** 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping 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. |