On 5/4/19 3:36 PM, Vinnie Falco via Boost wrote:
A crashing defect in Beast was discovered shortly after release:
https://github.com/boostorg/beast/issues/1599
It happens under high load when things happen at just the right time (or wrong time depending on how you look at it). It *will* eventually happen to any long-lived connection that sees enough traffic and timeouts. The fix is trivial:
https://github.com/vinniefalco/beast/commit/8620439f8e38db62713cff55a428bf8b...
Thanks to the detailed report we were able to write a unit test which reproduces it reliably.
Is this worth putting up a 1.70.1 for? The timeout feature is new in 1.70 and it is rather a shame that people might not be able to use it because of a defect.
Perhaps this is a good opportunity to craft and test a procedure for a single library update. This would be one small step in the direction of boost modularization. In theory this shouldn't be actually very hard if one can presume that the user has 1.70 installed. This is a pretty solid assumption since otherwise he wouldn't need to update anyway. Robert Ramey