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.

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

signal_set concurrency bug #418

Closed
vinipsmaker opened this issue Aug 8, 2019 · 2 comments
Closed

signal_set concurrency bug #418

vinipsmaker opened this issue Aug 8, 2019 · 2 comments

Comments

@vinipsmaker
Copy link
Contributor

I found a scenario where the detail::signal_set_service will fail to deliver the signal notification to the appropriate handlers. I wrote a small example illustrating the problem: https://gist.github.com/vinipsmaker/2ec8027f64f4bec4e2bb7fbc70d27fa8

If you remove the extra thread, it'll work.

@vinipsmaker
Copy link
Contributor Author

My example had a race. However that was not the problem. My original app didn't have this race.

I could fix the race in the example... However I'll just close the issue anyway given it no longer appears on Boost.Asio 1.76. I'll just reopen it with an updated example if it shows up again.

@timblechmann
Copy link

makes me wonder if this is related: boostorg/asio#403

vinipsmaker added a commit to vinipsmaker/emilua that referenced this issue Mar 1, 2023
The bug no longer seems to appear in Boost.Asio 1.76.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants