Fix memory leak in PerThreadPersistentClients #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello. I noticed two memory leaks:
thread.thread_variable_set(@key)
, but we read them viathread[@key]
. Since one is Thread-local and the other Fiber-local, we were never finding any clients to close@key
was leaking (https://redmine.ruby-lang.org/issues/19333)To fix both, i used this pattern that you have used previously used socketry/async-http@fcf231a#diff-df1daaada169fc5385e7257d57137dc5e11165a5551dda1ccc17f7546f1c360bR8
Types of Changes
Contribution