Daniel J. Hofmann e7d9e42a16 Fix race condition in osrm-routed HTTP server ... We had a similar issue a few month ago. Stumbled upon this by accident. It goes like this: - `output_buffer` is function-local - we pass it to async_write and leave the scope - `output_buffers` goes out of scope - bad things happen, sometimes The fix is to, again, put it inside the connection that handles itself via the enable_shared_from_this idiom. References: - http://www.boost.org/doc/libs/1_59_0/doc/html/boost_asio/reference/async_write/overload1.html - https://github.com/Project-OSRM/osrm-backend/pull/1690		2016-01-13 23:21:45 +01:00
..
contractor	Rips out dead code from the container.hpp and creates for_each_pai.hpp	2016-01-11 20:14:35 +01:00
datastore	Run clang-format	2016-01-08 01:31:57 +01:00
engine	Rips out dead code from the container.hpp and creates for_each_pai.hpp	2016-01-11 20:14:35 +01:00
extractor	Rips out dead code from the container.hpp and creates for_each_pai.hpp	2016-01-11 20:14:35 +01:00
osrm	Run clang-format	2016-01-08 01:31:57 +01:00
server	Fix race condition in osrm-routed HTTP server	2016-01-13 23:21:45 +01:00
util	Define compile-time constants for coordinate calculation only once	2016-01-12 19:59:02 +01:00