-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Confirm that resource usage is still 0 before retiring #17
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was trying to avoid the extra hash lookup but this seems correct.
I had to revert this as it was breaking the
Do you mind taking a look at what's going on? |
Perhaps related test failures: https://github.com/socketry/async-pool/actions/runs/8776705889/job/24080605709 Might indicate race conditions in the implementation or tests. |
This PR adds a secondary check that a resource is unused during pruning.
Per existing comments, retiring resources may cause context switches. When there are 2+ resources that are eligible for retiring, a context switch caused by retiring an earlier resource may also allow a later resource in the
unused
list to be reused. That may in turn cause a newly reused resource to be errantly retired and closed while in use.Types of Changes
Contribution