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

[BUG] - Resources are not properly refcounted #44

Open
4 tasks done
bSchnepp opened this issue Dec 11, 2022 · 2 comments
Open
4 tasks done

[BUG] - Resources are not properly refcounted #44

bSchnepp opened this issue Dec 11, 2022 · 2 comments
Assignees

Comments

@bSchnepp
Copy link
Owner

Issue Checklist

  • A related or similar issue is not already marked as open
  • The steps to reproduce have been tested, and do produce the issue described
  • If relevant, graphical issues have a screenshot presented as well. Text-only issues have the text and it's correct version listed within a Markdown code block section
  • The most recent commit on the master branch the bug is present in, with it's commit hash, is listed in this report

=====================================================
Bug Description
A process can quickly exhaust all available resources on a handle, effectively doing a denial of service on any other user of that resource backed by that handle.

To Reproduce
Please list the steps to produce the bug below:

  1. Write an initial process which opens a named port
  2. Constantly try to re-open it
  3. Eventually, resources on it will be exhausted

Screenshots
If relevant, please provide screenshots here.

Expected behavior
A handle can't be overloaded

Additional information
Any additional information should be placed here.

@bSchnepp
Copy link
Owner Author

A simple fix for this would be to simply re-open the same handle, if already open, instead of allocating new ones.

@bSchnepp
Copy link
Owner Author

The problem that currently appears to happen is that a client can open up a bunch of ClientConnections and close them, but it is possible that the corresponding ServerConnection never closes, and thus any Connection can no longer be made. Since no server currently polls it's own connections to check for validity, these don't close as expected.

@bSchnepp bSchnepp self-assigned this Dec 18, 2022
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