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

Socket cleanup #1

Open
reynoldsbd opened this issue Jan 13, 2019 · 2 comments
Open

Socket cleanup #1

reynoldsbd opened this issue Jan 13, 2019 · 2 comments

Comments

@reynoldsbd
Copy link
Owner

The bridge socket is not automatically cleaned up after process termination.

This is partially mitigated by attempting to delete the socket before opening it (making sure we start clean each time). However, even this seems to fail sometimes with the following OS error message: "Only one usage of each socket address (protocol/network address/port) is normally permitted."

Not sure why I'm seeing this particular message, especially since it's happening right after deleting the socket in question. One thing to try before digging deeper is gracefully shutting down the socket. This would require catching and handling a termination signal.

@reynoldsbd
Copy link
Owner Author

Consider using ctrlc.

@reynoldsbd
Copy link
Owner Author

Task Scheduler appears to simply terminate tasks. This method does not allow for cleanup code to be run.

Workaround would be to implement a Windows service and properly handle events.

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