Bug 1101783

Summary: [abrt] evolution-data-server: ews_get_attachments(): evolution-calendar-factory killed by SIGSEGV
Product: [Fedora] Fedora Reporter: EMR_Fedora <erecio>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fabiano, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f135c857d1da02ec786e85601d43ce26c5224aec
Whiteboard: abrt_hash:8bfbf73c9801d25478ac4eaed604a25b2c574360
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-28 08:43:00 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: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description EMR_Fedora 2014-05-27 22:58:24 UTC 
Description of problem:
Opened a large email

Version-Release number of selected component:
evolution-data-server-3.10.4-3.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory
crash_function: ews_get_attachments
executable:     /usr/libexec/evolution-calendar-factory
kernel:         3.14.4-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 ews_get_attachments at e-cal-backend-ews.c:3275
 #1 ews_cal_sync_get_items_sync at e-cal-backend-ews.c:3774
 #2 cal_backend_ews_process_folder_items at e-cal-backend-ews.c:3829
 #3 ews_start_sync_thread at e-cal-backend-ews.c:3934
 #4 g_thread_proxy at gthread.c:798

Potential duplicate: bug 905047
Comment 1 EMR_Fedora 2014-05-27 22:58:26 UTC 
Created attachment 899748 [details]
File: backtrace
Comment 2 EMR_Fedora 2014-05-27 22:58:27 UTC 
Created attachment 899749 [details]
File: cgroup
Comment 3 EMR_Fedora 2014-05-27 22:58:28 UTC 
Created attachment 899750 [details]
File: core_backtrace
Comment 4 EMR_Fedora 2014-05-27 22:58:29 UTC 
Created attachment 899751 [details]
File: dso_list
Comment 5 EMR_Fedora 2014-05-27 22:58:30 UTC 
Created attachment 899752 [details]
File: environ
Comment 6 EMR_Fedora 2014-05-27 22:58:30 UTC 
Created attachment 899753 [details]
File: exploitable
Comment 7 EMR_Fedora 2014-05-27 22:58:31 UTC 
Created attachment 899754 [details]
File: limits
Comment 8 EMR_Fedora 2014-05-27 22:58:32 UTC 
Created attachment 899755 [details]
File: maps
Comment 9 EMR_Fedora 2014-05-27 22:58:33 UTC 
Created attachment 899756 [details]
File: open_fds
Comment 10 EMR_Fedora 2014-05-27 22:58:34 UTC 
Created attachment 899757 [details]
File: proc_pid_status
Comment 11 EMR_Fedora 2014-05-27 22:58:35 UTC 
Created attachment 899758 [details]
File: var_log_messages
Comment 12 Milan Crha 2014-05-28 08:43:00 UTC 
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

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