Skip to content

Check for previously noted socket race condition #120

Description

@aaaaalbert

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions