-
Notifications
You must be signed in to change notification settings - Fork 521
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
Uninitialize LossDetection earlier to cleanup Datagram frame #4316
Conversation
… removeing client callback
Since there are still leaks, even with this change, I feel like
|
I wonder if we need to add a |
DatagramSend is still called after QuicDatagramSendShutdown which touches released |
The |
There is still case of |
are cleaned by |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4316 +/- ##
==========================================
- Coverage 86.04% 85.06% -0.99%
==========================================
Files 56 56
Lines 15382 15384 +2
==========================================
- Hits 13236 13086 -150
- Misses 2146 2298 +152 ☔ View full report in Codecov by Sentry. |
Fixed! |
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.
LGTM. Thanks for making these changes!
I see there are a number of BVT failures. I"m rerunning them to see if they are real regressions or not. |
Linux XDP related is fixed by different PR |
src/core/loss_detection.c
Outdated
@@ -408,6 +409,7 @@ QuicLossDetectionOnPacketSent( | |||
"Sent packet metadata", | |||
SIZEOF_QUIC_SENT_PACKET_METADATA(TempSentPacket->FrameCount)); | |||
QuicLossDetectionRetransmitFrames(LossDetection, TempSentPacket, FALSE); | |||
QuicLossDetectionOnPacketDiscarded(LossDetection, TempSentPacket, FALSE, FALSE); |
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.
We talked in person about a slightly different way to do this. Please update. Thanks!
Description
App allocated buffer for Datagram Frame has been leaking due to
Testing
Ran local test. No leak detected. No leak found from my own memory tracker either.
./artifacts/bin/linux/x64_Debug_openssl3/spinquic both -timeout:600000 -repeat_count:20 -alloc_fail:100
./artifacts/bin/linux/x64_Debug_openssl/spinquic both -timeout:600000 -repeat_count:20 -alloc_fail:100
Let's see automation results
Documentation
N/A