Bug 661543 - [abrt] evolution-2.32.1-1.fc14: g_main_context_check: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.1-1.fc14: g_main_context_check: Process /usr/bin/evolut...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4e4cf0d3323f2238392c37d820a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-08 22:53 UTC by Geofrey
Modified: 2010-12-09 10:15 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-09 10:15:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (47.47 KB, text/plain)
2010-12-08 22:53 UTC, Geofrey
no flags Details

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.


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