On Sat, May 4, 2019 at 6:37 PM Vinnie Falco via Boost <boost@lists.boost.org> 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/8620439f8e38db62713cff55a428bf8b3dd70062>
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.
Boost releases are quite expensive and happen on a regular schedule. Releases happen every 4 months and people can get the latest from develop with the fix. That should be sufficient. - Jim