net: "semaphore timeout period has expired" on Windows

[taruti]

Long-standing http.Client connections appear to suffer from

WSARecv: tcp <some-ipaddress-and-port>: The semaphore timeout period has expired

with go1.1.1 on windows/386.

This is quite hard to reproduce, but is probably the same problem as issue #2057 was.

[bradfitz]

Comment 1:

It's not obvious whether this is specific to net/http, or is a general net issue. It
sounds like the latter.

Labels changed: added os-windows, removed priority-triage.

Status changed to Accepted.

[alexbrainman]

Comment 2:

No program to demonstrate, taruti?
Error message does not help me any. Perhaps others can help more.
Alex

[rsc]

Comment 3:

More information will make this much more likely to be fixed.

Labels changed: added go1.2maybe, suggested.

[rsc]

Comment 4:

Labels changed: added feature.

[robpike]

Comment 5:

Deferring to 1.3.

Labels changed: added go1.3maybe, removed go1.2maybe.

[robpike]

Comment 6:

Labels changed: removed go1.3maybe.

[rsc]

Comment 7:

Labels changed: added go1.3maybe.

[rsc]

Comment 8:

Labels changed: removed feature.

[rsc]

Comment 9:

Labels changed: added release-none, removed go1.3maybe.

[rsc]

Comment 10:

Labels changed: added repo-main.

[mikioh]

Closing. I think runtime-integrated network poller with IOCP fixed this issue.