-
-
Notifications
You must be signed in to change notification settings - Fork 415
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.
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
Fix bug in ASIO shutdown #4548
Fix bug in ASIO shutdown #4548
Conversation
Prior to this commit, when shutting down the ASIO subsystem, we ignored the result of our waiting to join on the ASIO thread's termination. By ignoring the result, in cases where the join failed, we would continue doing ASIO shutdown related activities while the ASIO system was still running. This was "not good".
@dipinhora is the interaction with the systematic testing asio shutdown ok with this change? |
Hi @SeanTAllen, The changelog - fixed label was added to this pull request; all PRs with a changelog label need to have release notes included as part of the PR. If you haven't added release notes already, please do. Release notes are added by creating a uniquely named file in the The basic format of the release notes (using markdown) should be:
Thanks. |
systematic testing shouldn't be impacted (i think) as it already works with how the asio shutdown process happens... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm not an expert on the failure conditions for ponyint_thread_join
and whether that same thread might be able to be successfully ponyint_thread_join
'd later on or not but this seems good to me..
Unless I am completely misreading the docs that I refreshed myself on, that shouldn't be possible. |
Prior to this commit, when shutting down the ASIO subsystem, we ignored the result of our waiting to join on the ASIO thread's termination.
By ignoring the result, in cases where the join failed, we would continue doing ASIO shutdown related activities while the ASIO system was still running.
This was "not good".