Bug 858881

Summary: [abrt] evolution-3.4.4-1.fc17: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Steven Hadfield <hadfieldster>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:59a2c8fbc3c617396290b0d50c71998851d10cd6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-16 06:55:34 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: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: var_log_messages
none
File: open_fds none

Description Steven Hadfield 2012-09-19 21:59:44 UTC 
Description of problem:
I have been having trouble with Evolution sometimes causing my entire X session to slow down (the X process CPU will continually stay high while Evolution is open). The issue seemed mitigated by running in express mode (--express), but this is the first time that it has segfaulted. Evolution had been running for a few hours this way (off and on usage; mostly running in the background), and then when I switched to it, it segfaulted immediately.

Version-Release number of selected component:
evolution-3.4.4-1.fc17

Additional info:
libreport version: 2.0.13
abrt_version:   2.0.12
backtrace_rating: 4
cmdline:        evolution --express
crash_function: folder_tree_selectable_update_actions
kernel:         3.5.3-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 folder_tree_selectable_update_actions at em-folder-tree.c
: #1 focus_tracker_selectable_update_actions at e-focus-tracker.c
: #2 focus_tracker_targets_received_cb at e-focus-tracker.c
: #3 request_targets_received_func at gtkclipboard.c
: #4 selection_received at gtkclipboard.c
: #8 g_signal_emit_by_name at gsignal.c
: #9 gtk_selection_retrieval_report at gtkselection.c
: #10 _gtk_selection_notify at gtkselection.c
: #11 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c
: #12 _g_closure_invoke_va at gclosure.c
Comment 1 Steven Hadfield 2012-09-19 21:59:47 UTC 
Created attachment 614601 [details]
File: core_backtrace
Comment 2 Steven Hadfield 2012-09-19 21:59:48 UTC 
Created attachment 614602 [details]
File: environ
Comment 3 Steven Hadfield 2012-09-19 21:59:49 UTC 
Created attachment 614603 [details]
File: limits
Comment 4 Steven Hadfield 2012-09-19 21:59:51 UTC 
Created attachment 614604 [details]
File: backtrace
Comment 5 Steven Hadfield 2012-09-19 21:59:52 UTC 
Created attachment 614605 [details]
File: cgroup
Comment 6 Steven Hadfield 2012-09-19 21:59:54 UTC 
Created attachment 614606 [details]
File: maps
Comment 7 Steven Hadfield 2012-09-19 21:59:55 UTC 
Created attachment 614607 [details]
File: dso_list
Comment 8 Steven Hadfield 2012-09-19 21:59:56 UTC 
Created attachment 614608 [details]
File: var_log_messages
Comment 9 Steven Hadfield 2012-09-19 21:59:57 UTC 
Created attachment 614609 [details]
File: open_fds
Comment 10 Milan Crha 2012-10-16 06:55:34 UTC 
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

With respect of the high CPU usage, could you try to change height/width of the preview panel by more than 50 pixels, whether it'll help, please? There is a known bug which is cased by certain size of the preview panel, when the shown message fits its area almost completely, but the underlying widget is fighting with the view whether to show scrollbars or not, which is causing high CPU usage. Maybe your issue is the same.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=638814