-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
fix: whep gathering failure leaks peer connections #3124
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3124 +/- ##
==========================================
- Coverage 55.57% 55.57% -0.01%
==========================================
Files 150 150
Lines 16822 16839 +17
==========================================
+ Hits 9349 9358 +9
- Misses 6735 6744 +9
+ Partials 738 737 -1 ☔ View full report in Codecov by Sentry. |
when read fails, client is not closed
Still leaking... Same thing, it's just slow to build up |
Seems fine now (running 20 minutes and no increase). It looks like the HTTPClient keeps idle open connections for future requests and does not clean them up unless CloseIdleConnections() is called. They would eventually die out, but that depends on GC and/or remote side closing, which is not ideal. 🤞 |
…ient.Read() or WHEPClient.Publish()
a96004d
to
fa24957
Compare
Thanks for this patch, i did the following changes:
I agree with you on the fact that This has been merged, thanks! |
This issue is mentioned in release v1.7.0 🚀 |
Tentative fix for #3118
It still leaks, but less; Here is what remains leaking: