Bug 661543

Summary: [abrt] evolution-2.32.1-1.fc14: g_main_context_check: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Geofrey <grburgos>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:4e4cf0d3323f2238392c37d820a495da82d6a672
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-09 10:15:35 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 Flags
File: backtrace none

Description Geofrey 2010-12-08 22:53:46 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: g_main_context_check
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.i686.PAE
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1291543403
uid: 500

How to reproduce
-----
1.chating on msn
2.have skype working as well.
3.
Comment 1 Geofrey 2010-12-08 22:53:48 UTC 
Created attachment 467608 [details]
File: backtrace
Comment 2 Milan Crha 2010-12-09 10:15:35 UTC 
Thanks for a bug report. The backtrace seems to suggest that this is some sort of memory corruption, because the crashing thread doesn't show anything useful. Other threads are either in idle or refreshing your MAPI folder.

I'm closing this, but if you could try to run evolution under valgrind, then maybe it'll show us something, though evolution is pretty slow when using valgrind, due to all the memory checking. One possible command you can use is:
   $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>/tmp/evo.log
where the /tmp/evo.log will contain the data captured from valgrind.