Bug 688160 - [abrt] evolution-2.32.2-1.fc14: magazine_chain_pop_head: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.2-1.fc14: magazine_chain_pop_head: Process /usr/bin/evo...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:44fdb3b2255e246a439bc780050...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-16 13:56 UTC by Jerry James
Modified: 2011-03-18 06:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-18 06:46:58 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (66.23 KB, text/plain)
2011-03-16 13:56 UTC, Jerry James
no flags Details

Description Jerry James 2011-03-16 13:56:45 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 67823 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 143753216 bytes
crash_function: magazine_chain_pop_head
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300283529
uid: 500

How to reproduce
-----
1. I clicked on the mail icon at the top left of my desktop.
2. The evolution frame had just started to draw when it crashed.
3.

Comment 1 Jerry James 2011-03-16 13:56:47 UTC
Created attachment 485738 [details]
File: backtrace

Comment 2 Milan Crha 2011-03-17 09:26:57 UTC
Thanks for a bug report. I see from the backtrace that this crashed while a message was constructed in your IMAP account. This seems to me like a coincidence crash, but if you can reproduce it, then even better, as I didn't see any similar crash for some time. I suppose valgrind may shed some light here too. You can run evolution under valgrind like this:
   $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt
Which, if you'll be able to reproduce it, will most likely show us where the memory corruption happened (I think it's a memory corruption, but no exact clue yet).

Comment 3 Jerry James 2011-03-17 15:21:15 UTC
No luck reproducing so far.  Since the crash has happened exactly once, I'm guessing it's somewhat unlikely to occur.  I'll keep trying, though, and will report back if valgrind manages to catch it.

Comment 4 Milan Crha 2011-03-18 06:46:58 UTC
Thanks for the update. These "sometimes-happen" bugs are always pity, I do not like them much. I'm closing this for now, but please reopen if you'll see it again, hopefully with valgrind log (though I agree that evolution is mostly unusable for regular work when running under valgrind).


Note You need to log in before you can comment on or make changes to this bug.