Looks like most of the leaks are gone, thanks! But I'm still seeing problems. About one in every 10-15 runs of the load test on my 8-core Vivid machine, I get the output below from valgrind. Looks like there is a race condition somewhere. ==13111== ==13111== HEAP SUMMARY: ==13111== in use at exit: 174,592 bytes in 1,968 blocks ==13111== total heap usage: 317,581 allocs, 315,613 frees, 54,709,429 bytes allocated ==13111== ==13111== 174,528 (81 direct, 174,447 indirect) bytes in 1 blocks are definitely lost in loss record 65 of 65 ==13111== at 0x4C2B100: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==13111== by 0x4E878E7: boost::asio::detail::thread_info_base::allocate(boost::asio::detail::thread_info_base*, unsigned long) (thread_info_base.hpp:60) ==13111== by 0x4E879F6: boost::asio::asio_handler_allocate(unsigned long, ...) (handler_alloc_hook.ipp:50) ==13111== by 0x4E855F0: void* boost_asio_handler_alloc_helpers::allocate const&, std::chrono::duration > const&)::{lambda(boost::system::error_code const&)#1}>(unsigned long, curl::multi::Handle::Private::Timeout::Private::async_wait_for(std::weak_ptr const&, std::chrono::duration > const&)::{lambda(boost::system::error_code const&)#1}&) (handler_alloc_helpers.hpp:37) ==13111== by 0x4E8513C: void boost::asio::detail::deadline_timer_service >::async_wait const&, std::chrono::duration > const&)::{lambda(boost::system::error_code const&)#1}>(boost::asio::detail::deadline_timer_service >::implementation_type&, curl::multi::Handle::Private::Timeout::Private::async_wait_for(std::weak_ptr const&, std::chrono::duration > const&)::{lambda(boost::system::error_code const&)#1}&) (deadline_timer_service.hpp:185) ==13111== by 0x4E84E71: boost::asio::async_result const&, std::chrono::duration > const&)::{lambda(boost::system::error_code const&)#1}, void (boost::system::error_code)>::type>::type boost::asio::deadline_timer_service >::async_wait const&, std::chrono::duration > const&)::{lambda(boost::system::error_code const&)#1}>(boost::asio::detail::deadline_timer_service >::implementation_type&, boost::asio::handler_type&&) (deadline_timer_service.hpp:149) ==13111== by 0x4E84D63: boost::asio::async_result const&, std::chrono::duration > const&)::{lambda(boost::system::error_code const&)#1}, void (boost::system::error_code)>::type>::type boost::asio::basic_deadline_timer, boost::asio::deadline_timer_service > >::async_wait const&, std::chrono::duration > const&)::{lambda(boost::system::error_code const&)#1}>(boost::asio::handler_type&&) (basic_deadline_timer.hpp:508) ==13111== by 0x4E83CC8: curl::multi::Handle::Private::Timeout::Private::async_wait_for(std::weak_ptr const&, std::chrono::duration > const&) (multi.cpp:400) ==13111== by 0x4E83A02: curl::multi::Handle::Private::Timeout::async_wait_for(std::shared_ptr const&, std::chrono::duration > const&) (multi.cpp:371) ==13111== by 0x4E83EA7: curl::multi::Handle::Private::timer_callback(void*, long, void*) (multi.cpp:434) ==13111== by 0x656B204: ??? (in /usr/lib/x86_64-linux-gnu/libcurl.so.4.3.0) ==13111== by 0x656E5F7: curl_multi_socket_action (in /usr/lib/x86_64-linux-gnu/libcurl.so.4.3.0) ==13111== ==13111== LEAK SUMMARY: ==13111== definitely lost: 81 bytes in 1 blocks ==13111== indirectly lost: 174,447 bytes in 1,965 blocks ==13111== possibly lost: 0 bytes in 0 blocks ==13111== still reachable: 64 bytes in 2 blocks ==13111== suppressed: 0 bytes in 0 blocks ==13111== Reachable blocks (those to which a pointer was found) are not shown. ==13111== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==13111== ==13111== For counts of detected and suppressed errors, rerun with: -v ==13111== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)