Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Termination when deleting websocket callback client #701

Closed
Bobface opened this issue Feb 16, 2018 · 3 comments
Closed

Termination when deleting websocket callback client #701

Bobface opened this issue Feb 16, 2018 · 3 comments

Comments

@Bobface
Copy link

Bobface commented Feb 16, 2018

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?
@whoan whoan mentioned this issue Mar 25, 2019
Merged
@whoan
Copy link
Contributor

whoan commented Mar 29, 2019

Did you happen to test if the problem is solved in v2.10.12 @Bobface ?

@Bobface
Copy link
Author

Bobface commented Mar 29, 2019

Sorry I have switched to Boost.Beast since this bug

@whoan
Copy link
Contributor

whoan commented Mar 29, 2019

I think this issue should be closed in that case

@Bobface Bobface closed this as completed Mar 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@whoan @Bobface