Bug 4344 – Sockets with multiple threads report missing/failed WSAStartup

Status
RESOLVED
Resolution
FIXED
Severity
normal
Priority
P2
Component
phobos
Product
D
Version
D2
Platform
x86_64
OS
Windows
Creation time
2010-06-18T21:02:00Z
Last change time
2010-11-08T05:18:37Z
Assigned to
repeatedly
Creator
adrian

Attachments

IDFilenameSummaryContent-TypeSize
666socket_bug.zipsource for server and client to reproduce this issueapplication/x-zip-compressed1409

Comments

Comment #0 by adrian — 2010-06-18T21:02:30Z
Created attachment 666 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.
Comment #1 by menodinulla — 2010-07-10T21:17:09Z
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.
Comment #2 by r.sagitario — 2010-08-10T01:34:13Z
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...
Comment #3 by schveiguy — 2010-10-19T06:18:55Z
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.
Comment #4 by spam — 2010-10-30T18:08:34Z
*** Issue 4975 has been marked as a duplicate of this issue. ***
Comment #5 by schveiguy — 2010-11-08T05:18:37Z
*** Issue 5183 has been marked as a duplicate of this issue. ***