Bug 1165725

Summary: [abrt] evolution-data-server: memset(): evolution-calendar-factory killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Tim Waugh <twaugh>
Component: evolution-data-serverAssignee: Milan Crha <mcrha>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d63f4dee26d297555181ee50417fad166e963e36
Whiteboard: abrt_hash:b070fc7fa36cfd055e71da044baed5cf35ebaccb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-20 10:05:46 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 Tim Waugh 2014-11-19 14:36:55 UTC 
Version-Release number of selected component:
evolution-data-server-3.12.8-1.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory
crash_function: memset
executable:     /usr/libexec/evolution-calendar-factory
kernel:         3.17.3-300.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 memset at ../sysdeps/x86_64/memset.S:64
 #2 e_memchunk_alloc0 at e-memory.c:149
 #3 e_sexp_result_new at e-sexp.c:189
 #4 func_occur_in_time_range at e-cal-backend-sexp.c:212
 #5 e_sexp_term_eval at e-sexp.c:783
 #6 e_sexp_eval at e-sexp.c:1699
 #7 e_cal_backend_sexp_match_comp at e-cal-backend-sexp.c:1260
 #8 e_data_cal_view_component_matches at e-data-cal-view.c:952
 #9 e_cal_backend_notify_component_created at e-cal-backend.c:4273
 #10 put_server_comp_to_cache at e-cal-backend-caldav.c:3239

Potential duplicate: bug 1079048
Comment 1 Tim Waugh 2014-11-19 14:37:01 UTC 
Created attachment 958986 [details]
File: backtrace
Comment 2 Tim Waugh 2014-11-19 14:37:02 UTC 
Created attachment 958987 [details]
File: cgroup
Comment 3 Tim Waugh 2014-11-19 14:37:06 UTC 
Created attachment 958988 [details]
File: core_backtrace
Comment 4 Tim Waugh 2014-11-19 14:37:08 UTC 
Created attachment 958989 [details]
File: dso_list
Comment 5 Tim Waugh 2014-11-19 14:37:09 UTC 
Created attachment 958990 [details]
File: environ
Comment 6 Tim Waugh 2014-11-19 14:37:10 UTC 
Created attachment 958991 [details]
File: exploitable
Comment 7 Tim Waugh 2014-11-19 14:37:12 UTC 
Created attachment 958992 [details]
File: limits
Comment 8 Tim Waugh 2014-11-19 14:37:15 UTC 
Created attachment 958993 [details]
File: maps
Comment 9 Tim Waugh 2014-11-19 14:37:16 UTC 
Created attachment 958994 [details]
File: open_fds
Comment 10 Tim Waugh 2014-11-19 14:37:17 UTC 
Created attachment 958995 [details]
File: proc_pid_status
Comment 11 Tim Waugh 2014-11-19 14:37:19 UTC 
Created attachment 958996 [details]
File: var_log_messages
Comment 12 Milan Crha 2014-11-20 10:05:46 UTC 
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate. I'm still not able to reproduce this myself, but my CalDAV calendars do not change that rapidly here, which partly explains it.

*** This bug has been marked as a duplicate of bug 1013213 ***