Created attachment 666 [details] source for server and client to reproduce this issue Hello, I encountered a strange problem dealing with sockets and threads under Windows (I use 64-bit 7 Pro). The server socket successfully accepts a connection and passes obtained socket to newly created thread, which deals with it correctly. However, the server socket then breaks with the exception on any next operation. The SocketException.errorCode is always 10093, which stands for missing or failed WSAStartup. Indeed, when I place WSAStartup after accepting connection, it works well (but most probably needs matching WSACleanup() call). The single-threaded version also presents no problems. I tried with DMD 2.046 and 2.047 with same result. I attach example sources of both server and client showing the issue.
I also encountered same problem on Winsows XP. Sample: ---------------------------------------------------- import core.thread; import std.socket; void main() { auto thread = new Thread({}); thread.start(); thread.join(); auto socket = new TcpSocket; } ---------------------------------------------------- Results: ---------------------------------------------------- std.socket.SocketException: Unable to create socket ---------------------------------------------------- And I found following code in /trunk/phobos/std/socket.d. 193 static ~this() 194 { 195 version(Win32) 196 { 197 WSACleanup(); 198 } 199 } 200 I think that "shared static ~this()" is correct.
After several hours of debugging I found the problem with the non-shared destructor aswell. "shared static ~this" seems to do the trick for now, but when building a DLL, unloading it will also kill connections of the whole application. I'd say the calls to WSAStartup and WSACleanup should be explicite. Fortunately, in my case, the DLL is never unloaded...
Fixed in changeset http://www.dsource.org/projects/phobos/changeset/2107 This does not fix the DLL issue, but phobos is not DLL friendly anyways. If you wish, open a separate issue for that.
*** Issue 4975 has been marked as a duplicate of this issue. ***
*** Issue 5183 has been marked as a duplicate of this issue. ***