Bug 859200 - [abrt] evolution-3.4.4-2.fc17: sftk_FreeContext: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Summary: [abrt] evolution-3.4.4-2.fc17: sftk_FreeContext: Process /usr/bin/evolution w...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d1d78978fee5923024a3765276b...
: 866020 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-20 19:24 UTC by Mark van Rossum
Modified: 2012-10-17 06:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-16 09:50:46 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: core_backtrace (3.19 KB, text/plain)
2012-09-20 19:24 UTC, Mark van Rossum 		no flags Details
File: environ (3.44 KB, text/plain)
2012-09-20 19:24 UTC, Mark van Rossum 		no flags Details
File: limits (1.29 KB, text/plain)
2012-09-20 19:24 UTC, Mark van Rossum 		no flags Details
File: backtrace (63.04 KB, text/plain)
2012-09-20 19:24 UTC, Mark van Rossum 		no flags Details
File: cgroup (130 bytes, text/plain)
2012-09-20 19:24 UTC, Mark van Rossum 		no flags Details
File: maps (96.71 KB, text/plain)
2012-09-20 19:24 UTC, Mark van Rossum 		no flags Details
File: dso_list (20.99 KB, text/plain)
2012-09-20 19:24 UTC, Mark van Rossum 		no flags Details
File: open_fds (2.16 KB, text/plain)
2012-09-20 19:24 UTC, Mark van Rossum 		no flags Details
File: var_log_messages (306 bytes, text/plain)
2012-09-20 19:24 UTC, Mark van Rossum 		no flags Details
View All

Description Mark van Rossum 2012-09-20 19:24:10 UTC 
Description of problem:
Scrolling long email

Version-Release number of selected component:
evolution-3.4.4-2.fc17

Additional info:
libreport version: 2.0.13
abrt_version:   2.0.12
backtrace_rating: 4
cmdline:        evolution
crash_function: sftk_FreeContext
kernel:         3.5.3-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #5 sftk_FreeContext at pkcs11u.c
: #6 sftk_DestroySession at pkcs11u.c
: #7 sftk_FreeSession at pkcs11u.c
: #8 NSC_CloseSession at pkcs11.c
: #10 pk11_CloseSession at pk11obj.c
: #12 PK11_DestroyContext at pk11cxt.c
: #13 ssl3_DestroyCipherSpec at ssl3con.c
: #14 ssl3_DestroySSL3Info at ssl3con.c
: #15 ssl_DestroySocketContents at sslsock.c
: #16 ssl_FreeSocket at sslsock.c
Comment 1 Mark van Rossum 2012-09-20 19:24:13 UTC 
Created attachment 615061 [details]
File: core_backtrace
Comment 2 Mark van Rossum 2012-09-20 19:24:15 UTC 
Created attachment 615062 [details]
File: environ
Comment 3 Mark van Rossum 2012-09-20 19:24:17 UTC 
Created attachment 615063 [details]
File: limits
Comment 4 Mark van Rossum 2012-09-20 19:24:20 UTC 
Created attachment 615064 [details]
File: backtrace
Comment 5 Mark van Rossum 2012-09-20 19:24:22 UTC 
Created attachment 615065 [details]
File: cgroup
Comment 6 Mark van Rossum 2012-09-20 19:24:25 UTC 
Created attachment 615066 [details]
File: maps
Comment 7 Mark van Rossum 2012-09-20 19:24:28 UTC 
Created attachment 615067 [details]
File: dso_list
Comment 8 Mark van Rossum 2012-09-20 19:24:30 UTC 
Created attachment 615068 [details]
File: open_fds
Comment 9 Mark van Rossum 2012-09-20 19:24:32 UTC 
Created attachment 615069 [details]
File: var_log_messages
Comment 10 Milan Crha 2012-10-16 07:18:40 UTC 
Thanks for a bug report. I see in the backtrace start the actual crash happened at the end of message sending, on a memory corruption. It can be related to scrolling or not, it's hard to tell. Maybe the long message content caused the memory error. Is it possible to reproduce this with that particular message (though memory corruptions are usually caught "randomly", not immediately when the actual corruption happens.
Comment 11 Mark van Rossum 2012-10-16 08:44:37 UTC 
Sorry, can't reproduce it anymore.
Moved on to evolution 3.6.1 on fc18.

I suggest to mark as wontfix or similar, if the current report isn't useful.
Comment 12 Milan Crha 2012-10-16 09:50:46 UTC 
Thanks for the update. I'll close this, but feel free to reopen or file a new bug if you catch anything similar in 3.6.1+. Thanks in advance.
Comment 13 Milan Crha 2012-10-17 06:57:57 UTC 
*** Bug 866020 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.