1e2f2d7da0
When the boost ioservice is stopped, pending work notifications will not happen. This includes deadline timers, which would otherwise time out the now cancelled I/O operations. When this happens just after starting a new connect operation, this can leave that operations in a state where it won't receive either the completion notification nor a timeout, causing a hang. This is fixed by keeping a list of connections corresponding to the connect operations, and cancelling them before stopping the boost ioservice. Note that the list of these connections can grow unbounded, as they're never cleaned up. Cleaning them up would involve working out which connections do not have any pending work, and it's not quite clear yet how to go about this. |
||
|---|---|---|
| .. | ||
| demo | ||
| include | ||
| tests | ||
| LICENSE.txt | ||
| README.md | ||
epee - is a small library of helpers, wrappers, tools and and so on, used to make my life easier.