From time to time when I delete an websocket_callback_client I get SIGABRT because a thread in websocket_callback_client (m_thread in wspp_callback_client to be specific) gets deleted by websocket_callback_client's destructor while it is joinable (not finished). I always call close().get() on the client before deleting it. Also, the delete and close are done by an independent thread - not inside a close/message-handler.
Any ideas how this can happen?
From time to time when I
deleteanwebsocket_callback_clientI get SIGABRT because a thread in websocket_callback_client (m_threadinwspp_callback_clientto be specific) gets deleted bywebsocket_callback_client's destructor while it is joinable (not finished). I always callclose().get()on the client before deleting it. Also, thedeleteandcloseare done by an independent thread - not inside a close/message-handler.Any ideas how this can happen?