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

Ports not being released on stop? #25

Open
feichh opened this issue Jun 12, 2013 · 1 comment
Open

Ports not being released on stop? #25

feichh opened this issue Jun 12, 2013 · 1 comment

Comments

@feichh
Copy link

feichh commented Jun 12, 2013

Hi,
It seems to me that the listening sockets are kept open after i stop an isolate, until I force stop the app through the app settings.
This can cause EADDRINUSE errors, when a server is started again.

cheers

@paddybyers
Copy link
Owner

That's correct, and it's because the process itself doesn't exit. Apps that rely on the process exit to clean up will leak, so it is the responsibility of the app to close listeners on exit.

My plan was to extend libuv to track all open handles associated with an isolate, and forcibly close them down. I didn't get to do that, but it's part of the plan for migrating to 0.11.

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

2 participants