[
https://issues.apache.org/jira/browse/THRIFT-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955145#comment-15955145
]
ASF GitHub Bot commented on THRIFT-4164:
----------------------------------------
Github user jeking3 closed the pull request at:
https://github.com/apache/thrift/pull/1235
> Core in TSSLSocket cleanupOpenSSL when destroying a mutex used by openssl
> -------------------------------------------------------------------------
>
> Key: THRIFT-4164
> URL: https://issues.apache.org/jira/browse/THRIFT-4164
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.10.0
> Environment: Ubuntu 14.04, openssl (version 1.0.2k)
> Reporter: James E. King, III
> Assignee: James E. King, III
> Priority: Critical
> Labels: breaking_change
> Fix For: 0.11.0
>
>
> In a project where thrift is used, i was investigating a core in an assertion
> in apache::thrift::concurrency::~Mutex (pthread variety). The mutex in
> question was one of the locking mutexes that thrift gives to openssl. The
> core occurred in TSSLSocket::cleanupOpenSSL() where the mutexes are destroyed
> (on the last line).
> I suspect that we might be changing the locking callbacks too early in the
> cleanup process; perhaps one of the other cleanup calls that follows it would
> have released a mutex in some situations? In any case, this needs to be
> investigated and I am assigning it to myself.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
