Bug 1253419

Summary: [abrt] evolution: imapx_untagged(): evolution killed by SIGSEGV
Product: [Fedora] Fedora Reporter: andrew <formisc>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: lucilanga, mbarnes, mcrha, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/29156d96e8b702d1078d1d26dcd8e6c0a453cc78
Whiteboard: abrt_hash:41c74dabe5b192a4a5294e272b6b862003459b5b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-14 06:15:18 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

Description andrew 2015-08-13 16:30:35 UTC 
Description of problem:
left it running for a long time (2-3 weeks) and in the morning it was dead

Version-Release number of selected component:
evolution-3.12.11-1.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        evolution
crash_function: imapx_untagged
executable:     /usr/bin/evolution
kernel:         4.0.8-200.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 imapx_untagged at camel-imapx-server.c:3021
 #1 imapx_step at camel-imapx-server.c:3432
 #2 imapx_ready_to_read at camel-imapx-server.c:7673
 #7 imapx_parser_thread at camel-imapx-server.c:7789
 #8 g_thread_proxy at gthread.c:764
Comment 1 andrew 2015-08-13 16:30:37 UTC 
Created attachment 1062713 [details]
File: backtrace
Comment 2 andrew 2015-08-13 16:30:38 UTC 
Created attachment 1062714 [details]
File: cgroup
Comment 3 andrew 2015-08-13 16:30:39 UTC 
Created attachment 1062715 [details]
File: core_backtrace
Comment 4 andrew 2015-08-13 16:30:40 UTC 
Created attachment 1062716 [details]
File: dso_list
Comment 5 andrew 2015-08-13 16:30:41 UTC 
Created attachment 1062717 [details]
File: environ
Comment 6 andrew 2015-08-13 16:30:42 UTC 
Created attachment 1062718 [details]
File: exploitable
Comment 7 andrew 2015-08-13 16:30:43 UTC 
Created attachment 1062719 [details]
File: limits
Comment 8 andrew 2015-08-13 16:30:44 UTC 
Created attachment 1062720 [details]
File: maps
Comment 9 andrew 2015-08-13 16:30:45 UTC 
Created attachment 1062721 [details]
File: open_fds
Comment 10 andrew 2015-08-13 16:30:45 UTC 
Created attachment 1062722 [details]
File: proc_pid_status
Comment 11 Milan Crha 2015-08-14 06:15:18 UTC 
Thanks for a bug report. If I read the backtrace properly, then your server returned some response, which caused the crash in the IMAPx code. It doesn't mean it was the server issue, it could be caused by some consequences. The backtrace also shows that there was some message filtering, an ongoing move of it into INBOX/Cim_techops_dba_oncall, and an ongoing folder refresh.

Sadly, 3.12 is obsolete for the upstream, the current stable is 3.16.5, but it'll be replaced with the 3.18.0 soon, which has these parts heavily changed. The 3.18.x is for Fedora 23.