Skip to content
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

Check for previously noted socket race condition #120

Open
aaaaalbert opened this issue May 4, 2016 · 0 comments
Open

Check for previously noted socket race condition #120

aaaaalbert opened this issue May 4, 2016 · 0 comments

Comments

@aaaaalbert
Copy link
Collaborator

An old wiki page claimed:

There exists a potential race condition while repy attempts to cleanup a network socket.

Assume repy is bound to the IP/Port tuple (X,Y) and it closes the socket. If another process binds to (X,Y) while repy is waiting for the cleanup to occur it will appear as if the OS has not yet cleaned up the socket, and repy will block indefinitely. This is a very rare bug, and is hard to trigger since repy checks 5 times per second for the socket cleanup.

Let's check if this problem really / still exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant