Bug 1253419 - [abrt] evolution: imapx_untagged(): evolution killed by SIGSEGV
[abrt] evolution: imapx_untagged(): evolution killed by SIGSEGV
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
21
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Milan Crha
Fedora Extras Quality Assurance
https://retrace.fedoraproject.org/faf...
abrt_hash:41c74dabe5b192a4a5294e272b6...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-13 12:30 EDT by andrew
Modified: 2015-08-14 02:15 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-14 02:15:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (66.54 KB, text/plain)
2015-08-13 12:30 EDT, andrew
no flags Details
File: cgroup (191 bytes, text/plain)
2015-08-13 12:30 EDT, andrew
no flags Details
File: core_backtrace (34.27 KB, text/plain)
2015-08-13 12:30 EDT, andrew
no flags Details
File: dso_list (27.64 KB, text/plain)
2015-08-13 12:30 EDT, andrew
no flags Details
File: environ (1.79 KB, text/plain)
2015-08-13 12:30 EDT, andrew
no flags Details
File: exploitable (82 bytes, text/plain)
2015-08-13 12:30 EDT, andrew
no flags Details
File: limits (1.29 KB, text/plain)
2015-08-13 12:30 EDT, andrew
no flags Details
File: maps (167.24 KB, text/plain)
2015-08-13 12:30 EDT, andrew
no flags Details
File: open_fds (5.44 KB, text/plain)
2015-08-13 12:30 EDT, andrew
no flags Details
File: proc_pid_status (971 bytes, text/plain)
2015-08-13 12:30 EDT, andrew
no flags Details

  None (edit)
Description andrew 2015-08-13 12:30:35 EDT
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 12:30:37 EDT
Created attachment 1062713 [details]
File: backtrace
Comment 2 andrew 2015-08-13 12:30:38 EDT
Created attachment 1062714 [details]
File: cgroup
Comment 3 andrew 2015-08-13 12:30:39 EDT
Created attachment 1062715 [details]
File: core_backtrace
Comment 4 andrew 2015-08-13 12:30:40 EDT
Created attachment 1062716 [details]
File: dso_list
Comment 5 andrew 2015-08-13 12:30:41 EDT
Created attachment 1062717 [details]
File: environ
Comment 6 andrew 2015-08-13 12:30:42 EDT
Created attachment 1062718 [details]
File: exploitable
Comment 7 andrew 2015-08-13 12:30:43 EDT
Created attachment 1062719 [details]
File: limits
Comment 8 andrew 2015-08-13 12:30:44 EDT
Created attachment 1062720 [details]
File: maps
Comment 9 andrew 2015-08-13 12:30:45 EDT
Created attachment 1062721 [details]
File: open_fds
Comment 10 andrew 2015-08-13 12:30:45 EDT
Created attachment 1062722 [details]
File: proc_pid_status
Comment 11 Milan Crha 2015-08-14 02:15:18 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.