Bryan Call created TS-3855:
------------------------------

             Summary: Memory leak in HTTP/2 with the ProxyMutex
                 Key: TS-3855
                 URL: https://issues.apache.org/jira/browse/TS-3855
             Project: Traffic Server
          Issue Type: Bug
          Components: HTTP/2
            Reporter: Bryan Call


{code}
==27397== 80 bytes in 1 blocks are definitely lost in loss record 1,587 of 2,195
==27397==    at 0x4C2AD85: memalign (in 
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==27397==    by 0x4C2AE4D: posix_memalign (in 
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==27397==    by 0x4E60D21: ats_memalign (ink_memory.cc:100)
==27397==    by 0x4E610AF: ink_freelist_new (ink_queue.cc:239)
==27397==    by 0x5FEDF3: alloc (Allocator.h:120)
==27397==    by 0x5FEDF3: new_ProxyMutex (I_Lock.h:555)
==27397==    by 0x5FEDF3: Http2ClientSession::new_connection(NetVConnection*, 
MIOBuffer*, IOBufferReader*, bool) (Http2ClientSession.cc:124)
==27397==    by 0x608990: Http2SessionAccept::accept(NetVConnection*, 
MIOBuffer*, IOBufferReader*) (Http2SessionAccept.cc:58)
==27397==    by 0x608880: Http2SessionAccept::mainEvent(int, void*) 
(Http2SessionAccept.cc:76)
==27397==    by 0x7411DB: SSLNextProtocolTrampoline::ioCompletionEvent(int, 
void*) (SSLNextProtocolAccept.cc:99)
==27397==    by 0x75CBEF: handleEvent (I_Continuation.h:146)
==27397==    by 0x75CBEF: read_signal_and_update (UnixNetVConnection.cc:145)
==27397==    by 0x75CBEF: read_signal_done (UnixNetVConnection.cc:206)
==27397==    by 0x75CBEF: UnixNetVConnection::readSignalDone(int, NetHandler*) 
(UnixNetVConnection.cc:1006)
==27397==    by 0x73DFA1: SSLNetVConnection::net_read_io(NetHandler*, EThread*) 
(SSLNetVConnection.cc:540)
==27397==    by 0x74B729: NetHandler::mainNetEvent(int, Event*) (UnixNet.cc:516)
==27397==    by 0x78439A: handleEvent (I_Continuation.h:146)
==27397==    by 0x78439A: process_event (UnixEThread.cc:128)
==27397==    by 0x78439A: EThread::execute() (UnixEThread.cc:252)
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to