Bug 1544296

Summary: [abrt] Check validity of returned values in 'Folder Sizes' function
Product: [Fedora] Fedora Reporter: John Williams <jwilliams>
Component: evolution-ewsAssignee: Milan Crha <mcrha>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: alexl, caillon+fedoraproject, florianvanoudgaarden, lucilanga, mcrha, rhughes, rstrode, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/070fa5f9b329b4b8f75e7114f1062e840596e0d4
Whiteboard: abrt_hash:dcf44496071c069c0dcfbd59a062346e361fb5c4;VARIANT_ID=workstation;
Fixed In Version: evolution-ews-3.27.91 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-12 11:54:48 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
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description John Williams 2018-02-12 01:29:44 UTC 
Description of problem:
No idea

Version-Release number of selected component:
evolution-3.26.4-1.fc27

Additional info:
reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        evolution
crash_function: ews_settings_get_folder_sizes_thread
executable:     /usr/bin/evolution
journald_cursor: s=e8119c474de748038dfe0a0fef31f304;i=10af59;b=fd174540ee4c4640a6d9bdf6f0255cb8;m=4ac79320c5;t=564f9acb90634;x=f10b616de7bda1ed
kernel:         4.14.13-300.fc27.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (2 frames)
 #0 ews_settings_get_folder_sizes_thread at /usr/src/debug/evolution-ews-3.26.4-1.fc27.x86_64/src/configuration/e-ews-config-utils.c:697
 #1 g_thread_proxy at gthread.c:784
Comment 1 John Williams 2018-02-12 01:29:50 UTC 
Created attachment 1394759 [details]
File: backtrace
Comment 2 John Williams 2018-02-12 01:29:51 UTC 
Created attachment 1394760 [details]
File: cgroup
Comment 3 John Williams 2018-02-12 01:29:53 UTC 
Created attachment 1394761 [details]
File: core_backtrace
Comment 4 John Williams 2018-02-12 01:29:55 UTC 
Created attachment 1394762 [details]
File: cpuinfo
Comment 5 John Williams 2018-02-12 01:29:57 UTC 
Created attachment 1394763 [details]
File: dso_list
Comment 6 John Williams 2018-02-12 01:29:58 UTC 
Created attachment 1394764 [details]
File: environ
Comment 7 John Williams 2018-02-12 01:30:00 UTC 
Created attachment 1394765 [details]
File: exploitable
Comment 8 John Williams 2018-02-12 01:30:01 UTC 
Created attachment 1394766 [details]
File: limits
Comment 9 John Williams 2018-02-12 01:30:04 UTC 
Created attachment 1394767 [details]
File: maps
Comment 10 John Williams 2018-02-12 01:30:05 UTC 
Created attachment 1394768 [details]
File: mountinfo
Comment 11 John Williams 2018-02-12 01:30:07 UTC 
Created attachment 1394769 [details]
File: open_fds
Comment 12 John Williams 2018-02-12 01:30:08 UTC 
Created attachment 1394770 [details]
File: proc_pid_status
Comment 13 Milan Crha 2018-02-12 11:54:48 UTC 
Thanks for a bug report. If I read the backtrace and the related code properly, then you've used either right-click EWS account->Folder Sizes... context menu option or in EWS account Properties->EWS Settings->Folder Sizes button. The problem seems to be that one of the folders failed to return some folder, which led to this crash.

I could not reproduce this myself, but I think I see the weak point in the code, thus I changed it for 3.27.91+ with commit:
https://git.gnome.org/browse/evolution-ews/commit/?id=4eaf3ee
Comment 14 Florian van Oudgaarden 2018-04-04 11:25:41 UTC 
*** Bug 1563637 has been marked as a duplicate of this bug. ***