Fix ASIO usage for uWS::Loop::defer. #204
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was resulting it being called with the wrong address once uWS::Loop::wakeupCb was called.
I observed that uWS::Loop::defer was not ever triggering, and tracked it down to a memory address difference between the loop and what
uWS::Loop::wakeupCb
was being called with.I'm not sure this is the proper fix - but it helps my use-case - is it reasonable for all uses (not just uWebSockets)? Also, IIUC, not sure why others are not experiencing this issue (perhaps low usage of ASIO?).
This is the repro case, that now behaves properly with the fix (i.e. it exits, and does not get stuck when using Defer).