A suspected memory leak occurred when the connection was timeout disconnected

[noah-hwang]

The following code appears to have a memory leak.
The scene is as follows:
1.The client initiates a connection and the connection times out，QUIC_CONNECTION_EVENT_SHUTDOWN_COMPLETE event callback.
2.Then actively call ConnectionClose, and DATAPATH_IO_RECV IoType callback, IoResult is EORROR_OPERATION_ABORTED.
3.Final entry CxPlatDataPathSocketProcessReceive, the RecvContext is not release while SocketContext release.
Whether memory leaks are caused by each timeout disconnection.
Thanks!

void
CxPlatDataPathSocketProcessReceive(
    _In_ DATAPATH_RX_IO_BLOCK* IoBlock,
    _In_ uint16_t BytesTransferred,
    _In_ ULONG IoResult
    )
{
    CXPLAT_SOCKET_PROC* SocketProc = IoBlock->SocketProc;

    CXPLAT_DBG_ASSERT(!SocketProc->Freed);
    if (!CxPlatRundownAcquire(&SocketProc->RundownRef)) {
        //
        // Even though we can't process the completion (because the socket is
        // cleaning up) we still need to release the reference it has on the
        // context.
        //
        CxPlatSocketContextRelease(SocketProc);
        return;
    }

[nibanks]

I believe everything should be cleaned up when the socket context and parent socket are cleaned up. Do you have data to show this isn't the case? We run many of our tests with ASAN, and they inform us when we have a leak, and I've never seen one here.

[noah-hwang]

Thank you for your reply!
In the case of server IP address is unreachable, client calls api repeatedly as follow:
ConnectionOpen -> ConnectionStart -> ConnectionClose
But not call ConfigurationClose、RegistrationClose and MsQuicClose.

Visual Studio Performance Profiler monitor show memory growth in CxPlatSocketAllocRecvContext.

This is what I found by adding debug log.
I add static variable count.
Increment in CxPlatSocketAllocRecvContext.
Subtract in CxPlatSocketFreeRecvContext.
Found that RecvContext Alloc but not Free.