Bug 607187
| Summary: | [abrt] abort evolution-2.30.1-6.fc13: header_raw_free, camel_header_raw_clear, camel_filter_search_match | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Greg Ennis <pomec> | ||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 13 | CC: | adellam, alejandro.perez.torres, alfredo.pons, ambijat, andrew.jones11235, bacaro, badandye, csuwhm, dudko, dwayne, engine.games, eyeneeserver, f.demiralp, fedora.bugreports, goran.wallin.dev, jeffrey.t.kirsher, kmaraas, lahtis, luca.botti, lucilanga, mbarnes, mcrha, milan, naoki, ov10fac, pmpcdg, psj, silverkriss, vpvainio | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | abrt_hash:26be3e33a7dbf525303f19b8bc5b6b636669b3c1 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-06-27 18:48:42 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Greg Ennis
2010-06-23 13:21:27 UTC
Created attachment 426271 [details]
File: backtrace
See also Bug 604430 - the combination of fc13 and this evolution is causing evolution to crash as many as 5 times per day. Is there anything I can do to help resolve this bug. Thank you for your work ---- Greg Ennis Thanks for a bug report. It seems it has some trouble while filtering messages, similar with bug #604430, though there it's slightly earlier. Could you try to run evolution as this, please: $ G_SLICE=always-malloc valgrind evolution &>evo.log which will track the issue and hopefully tell us where the memory was freed (in the evo.log file)? The only thing is that it'll probably not crash, but the log will contain some information about accessing already freed memory or something like that. Please remove from there any private information you may find there, even this kind of log usually doesn't contain any. Thanks in advance. Please note that the crash may not occur always, it may depends on messages you received and whether they were filtered or not. (Your above crash backtrace shows one specific filter which was under go during the abort.) *** Bug 584649 has been marked as a duplicate of this bug. *** *** Bug 585321 has been marked as a duplicate of this bug. *** *** Bug 585797 has been marked as a duplicate of this bug. *** *** Bug 587408 has been marked as a duplicate of this bug. *** *** Bug 587465 has been marked as a duplicate of this bug. *** *** Bug 587920 has been marked as a duplicate of this bug. *** *** Bug 590735 has been marked as a duplicate of this bug. *** *** Bug 592405 has been marked as a duplicate of this bug. *** *** Bug 595460 has been marked as a duplicate of this bug. *** *** Bug 596687 has been marked as a duplicate of this bug. *** *** Bug 596736 has been marked as a duplicate of this bug. *** *** Bug 598189 has been marked as a duplicate of this bug. *** *** Bug 598412 has been marked as a duplicate of this bug. *** *** Bug 598434 has been marked as a duplicate of this bug. *** *** Bug 598494 has been marked as a duplicate of this bug. *** *** Bug 598529 has been marked as a duplicate of this bug. *** *** Bug 598872 has been marked as a duplicate of this bug. *** *** Bug 599276 has been marked as a duplicate of this bug. *** *** Bug 599432 has been marked as a duplicate of this bug. *** *** Bug 599490 has been marked as a duplicate of this bug. *** *** Bug 599569 has been marked as a duplicate of this bug. *** *** Bug 600193 has been marked as a duplicate of this bug. *** *** Bug 600280 has been marked as a duplicate of this bug. *** *** Bug 601757 has been marked as a duplicate of this bug. *** *** Bug 606005 has been marked as a duplicate of this bug. *** *** Bug 612506 has been marked as a duplicate of this bug. *** *** Bug 612990 has been marked as a duplicate of this bug. *** *** Bug 615583 has been marked as a duplicate of this bug. *** *** Bug 616236 has been marked as a duplicate of this bug. *** *** Bug 623437 has been marked as a duplicate of this bug. *** *** Bug 623449 has been marked as a duplicate of this bug. *** *** Bug 623536 has been marked as a duplicate of this bug. *** *** Bug 627714 has been marked as a duplicate of this bug. *** *** Bug 629742 has been marked as a duplicate of this bug. *** *** Bug 632074 has been marked as a duplicate of this bug. *** *** Bug 632140 has been marked as a duplicate of this bug. *** *** Bug 634329 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. |