id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
3605,Boost.Asio: Static Initialization causes Deadlock during WSAStartup and other problems,ulrich.kroemer@…,chris_kohlhoff,"I am experiencing spurios deadlocks during static initialization of the do_init global instance (win_sock_init.hpp). 

The scenario is this:
I am using a static library version of Boost.Asio, which means that once my .dll gets loaded, the do_init global instance is initialized and a call to WSAStartup is made.

At the same time a different thread of the application is already in a call to WSAStartup and already holds the critical section inside the WSAStartup function. Now inside that critical section a call to load the old winsock.dll is made and so the other thread tries to gain the loader lock, which my thread currently is the owner of. Therefore the application deadlocks.

I know that this might actually be a problem of WSAStartup all together, however due to the static initialization there is no workaround to the problem, as the time when the call to WSAStartup is made can't be configured.",Bugs,closed,Boost 1.41.0,asio,Boost 1.53.0,Problem,fixed,deadlock asio WSAStartup,