You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Till Toenshoff (JIRA)" <ji...@apache.org> on 2017/09/26 17:59:00 UTC
[jira] [Updated] (MESOS-8020) ssl-client crashes a lot during the
libprocess tests (without being noticed)
[ https://issues.apache.org/jira/browse/MESOS-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Toenshoff updated MESOS-8020:
----------------------------------
Attachment: ssl-client_2017-09-26-195308_lobomacpro2.crash
ssl-client_2017-09-26-195308-1_lobomacpro2.crash
ssl-client_2017-09-26-195308-2_lobomacpro2.crash
ssl-client_2017-09-26-195308-3_lobomacpro2.crash
ssl-client_2017-09-26-195308-4_lobomacpro2.crash
ssl-client_2017-09-26-195321_lobomacpro2.crash
ssl-client_2017-09-26-195321-1_lobomacpro2.crash
ssl-client_2017-09-26-195321-2_lobomacpro2.crash
glog_v2.log
Attached crash-reports and glogv=2 logs.
> ssl-client crashes a lot during the libprocess tests (without being noticed)
> ----------------------------------------------------------------------------
>
> Key: MESOS-8020
> URL: https://issues.apache.org/jira/browse/MESOS-8020
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: Apple LLVM version 9.0.0 (clang-900.0.37)
> libevent 2.0.22 (installed via homebrew)
> openssl 1.0.2l (installed via homebrew)
> Reporter: Till Toenshoff
> Attachments: glog_v2.log, ssl-client_2017-09-26-195308-1_lobomacpro2.crash, ssl-client_2017-09-26-195308-2_lobomacpro2.crash, ssl-client_2017-09-26-195308-3_lobomacpro2.crash, ssl-client_2017-09-26-195308-4_lobomacpro2.crash, ssl-client_2017-09-26-195308_lobomacpro2.crash, ssl-client_2017-09-26-195321-1_lobomacpro2.crash, ssl-client_2017-09-26-195321-2_lobomacpro2.crash, ssl-client_2017-09-26-195321_lobomacpro2.crash
>
>
> The libprocess test-suite, when running on my machine causes plenty of crash reports in {{~/Library/Logs/DiagnosticReports}}. The test-suite runs through without issues in those cases.
> One test that 100% reproducibly triggers this is "SSLTest.ProtocolMismatch". After a single run of that test which ends "OK", I got anything from 6 to 8 new crash reports in that folder.
> Example:
> {noformat}
> Thread 9 Crashed:
> 0 libevent-2.0.5.dylib 0x000000010ff64aa0 bufferevent_write_buffer + 4
> 1 ssl-client 0x000000010eb69b58 process::network::internal::LibeventSSLSocketImpl::send(char const*, unsigned long)::$_5::operator()() const + 904 (libevent_ssl_socket.cpp:769)
> 2 ssl-client 0x000000010eb697bd void std::__1::__invoke_void_return_wrapper<void>::__call<process::network::internal::LibeventSSLSocketImpl::send(char const*, unsigned long)::$_5&>(process::network::internal::LibeventSSLSocketImpl::send(char const*, unsigned long)::$_5&&&) + 45 (__functional_base:360)
> 3 ssl-client 0x000000010eb69509 std::__1::__function::__func<process::network::internal::LibeventSSLSocketImpl::send(char const*, unsigned long)::$_5, std::__1::allocator<process::network::internal::LibeventSSLSocketImpl::send(char const*, unsigned long)::$_5>, void ()>::operator()() + 41 (functional:1552)
> 4 ssl-client 0x000000010e882a0b std::__1::function<void ()>::operator()() const + 123 (functional:1911)
> 5 ssl-client 0x000000010ebb1238 process::async_function(int, short, void*) + 984 (libevent.cpp:56)
> 6 libevent-2.0.5.dylib 0x000000010ff5d424 event_base_loop + 809
> 7 ssl-client 0x000000010ebb15d3 process::EventLoop::run() + 131 (libevent.cpp:98)
> 8 ssl-client 0x000000010ea17eb0 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (*)()> >(void*) + 528 (type_traits:4291)
> 9 libsystem_pthread.dylib 0x00007fff591246c1 _pthread_body + 340
> 10 libsystem_pthread.dylib 0x00007fff5912456d _pthread_start + 377
> 11 libsystem_pthread.dylib 0x00007fff59123c5d thread_start + 13
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)