Skip to content

/ go

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

net: "semaphore timeout period has expired" on Windows #5940

Closed
taruti opened this issue Jul 23, 2013 · 11 comments
Closed

net: "semaphore timeout period has expired" on Windows #5940

taruti opened this issue Jul 23, 2013 · 11 comments
Labels
FrozenDueToAge OS-Windows Suggested
Milestone
Go1.3

Comments

@taruti
Copy link
Contributor

@taruti taruti commented Jul 23, 2013 

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

This comment has been minimized.

Sign in to view
Copy link
Contributor

@bradfitz bradfitz commented Jul 23, 2013

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

This comment has been minimized.

Sign in to view
Copy link
Member

@alexbrainman alexbrainman commented Jul 24, 2013

Comment 2:

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

This comment has been minimized.

Sign in to view
Copy link
Contributor

@rsc rsc commented Jul 30, 2013

Comment 3:

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

Labels changed: added go1.2maybe, suggested.
@rsc

This comment has been minimized.

Sign in to view
Copy link
Contributor

@rsc rsc commented Jul 30, 2013

Comment 4:

Labels changed: added feature.
@robpike

This comment has been minimized.

Sign in to view
Copy link
Contributor

@robpike robpike commented Aug 20, 2013

Comment 5:

Deferring to 1.3.

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

This comment has been minimized.

Sign in to view
Copy link
Contributor

@robpike robpike commented Aug 20, 2013

Comment 6:

Labels changed: removed go1.3maybe.
@rsc

This comment has been minimized.

Sign in to view
Copy link
Contributor

@rsc rsc commented Nov 27, 2013

Comment 7:

Labels changed: added go1.3maybe.
@rsc

This comment has been minimized.

Sign in to view
Copy link
Contributor

@rsc rsc commented Nov 27, 2013

Comment 8:

Labels changed: removed feature.
@rsc

This comment has been minimized.

Sign in to view
Copy link
Contributor

@rsc rsc commented Dec 4, 2013

Comment 9:

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

This comment has been minimized.

Sign in to view
Copy link
Contributor

@rsc rsc commented Dec 4, 2013

Comment 10:

Labels changed: added repo-main.
@rsc rsc removed the os-windows label Apr 10, 2015
@rsc rsc added this to the Unplanned milestone Apr 10, 2015
@rsc rsc added OS-Windows and removed release-none labels Apr 10, 2015
@mikioh

This comment has been minimized.

Sign in to view
Copy link
Contributor

@mikioh mikioh commented Jun 19, 2015

Closing. I think runtime-integrated network poller with IOCP fixed this issue.
@mikioh mikioh closed this Jun 19, 2015
@mikioh mikioh modified the milestones: Go1.3, Unplanned Jun 19, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge OS-Windows Suggested
Projects
None yet
Milestone
  Go1.3
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants
@taruti @bradfitz @alexbrainman @rsc @robpike @mikioh @gopherbot
You can’t perform that action at this time.