Bug 662315
| Summary: | [abrt] evolution-2.32.1-1.fc14: magazine_chain_pop_head: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | pleabargain <dennisgdaniels> | ||||||||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | low | ||||||||||||||
| Version: | 14 | CC: | lucilanga, mbarnes, mcrha | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | i686 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:d5b8cac50e63f35dc5e0713d858fdf942d949c50 | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2012-03-30 15:00:17 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
pleabargain
2010-12-11 14:28:12 UTC
Created attachment 468150 [details]
File: backtrace
This might be also related to bug #662334. I do not know what you mean with "full task menu", but the backtrace shows that you were about to quit evolution and it failed to free an object, which led to the crash. Into what task list type are you entering the tasks, please? (On This Computer/CalDAV/...) And if reproducible, could you get a valgrind log of the running evolution when reproducing the issues, please? I believe it'll discover the cause. You can do that by this: $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>evo.log Please make sure you have installed debug-info packages for evolution-data-server and evolution. As running evolution under valgrind is pretty slow, then maybe try to run evolution in offline, to avoid some after-start operations being done, like new mail fetching. It depends on the task list type whether it's possible or not. Please attach the resulting evo.log file. Thanks in advance. Created attachment 468543 [details]
backtrace
back trace
gdb --batch --ex "t a a bt" -pid=4190 &> ~/Desktop/evo_hangingoneditcalendar.log
Created attachment 468544 [details]
gslice after evo cal hang
[user@localhost ~]$ G_SLICE=always-malloc valgrind --num-callers=50 evolution &> ~/Desktop/gslice_evo_aftercalendarhang.log
Segmentation fault (core dumped)<<<<<<<<is that normal?
Created attachment 468546 [details]
gslice after evo writing email hang
[user@localhost ~]$ G_SLICE=always-malloc valgrind --num-callers=50 evolution &> ~/Desktop/gslice_evo_writingemailhang.log
Segmentation fault (core dumped)<<<<<<<<this can't be good, can it?
Created attachment 468550 [details]
trying to close unfinished email and evo hangs
[user@localhost ~]$ G_SLICE=always-malloc valgrind --num-callers=50 evolution &> ~/Desktop/gslice_evo_writingemaihangnotrespondingaftertryingtodeleteunfinishedemail.log
Segmentation fault (core dumped)
comment #3 - shows evo in idle comment #4, comment #5, comment #6 - it crashed on invalid delete in libstdc++ called from /usr/lib/libmodman.so.0.0.0 - to be honest I do not know what it is. Maybe the 'evolution' wasn't picked evolution executable itself, but some wrapper script? (I see you run it as I told you, so might be fine from this point of view). That libmodman is "A simple library for managing C++ modules (plug-ins)", but evolution itself doesn't use C++, it's pure C with GObject-s. Backtrace analysis found this bug to be similar to bug #641532, closing as duplicate. Bugs which were found to be similar to this bug: empathy: bug #641532, bug #654592, bug #659212, bug #751552 evolution: bug #638846 gedit: bug #553412 gnome-shell: bug #756593, bug #768063 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 641532 *** |