Brian Geffon created TS-2795:
--------------------------------

             Summary: Leaking CacheVConnections
                 Key: TS-2795
                 URL: https://issues.apache.org/jira/browse/TS-2795
             Project: Traffic Server
          Issue Type: Bug
          Components: Cache
            Reporter: Brian Geffon


It appears there is a memory leak in 4.0.x, 4.2.x, and master leaking 
CacheVConnections resulting in IOBufAllocator leaking also, here is an example:
     allocated      |        in-use      | type size  |   free list name
--------------------|--------------------|------------|----------------------------------
           67108864 |                  0 |    2097152 | 
memory/ioBufAllocator[14]
           67108864 |           19922944 |    1048576 | 
memory/ioBufAllocator[13]
         4798283776 |           14155776 |     524288 | 
memory/ioBufAllocator[12]
         7281311744 |           98304000 |     262144 | 
memory/ioBufAllocator[11]
         1115684864 |          148242432 |     131072 | 
memory/ioBufAllocator[10]
         4974444544 |          379977728 |      65536 | memory/ioBufAllocator[9]
         9902751744 |         5223546880 |      32768 | memory/ioBufAllocator[8]
        14762901504 |        14762311680 |      16384 | memory/ioBufAllocator[7]
         6558056448 |         6557859840 |       8192 | memory/ioBufAllocator[6]
           41418752 |           30502912 |       4096 | memory/ioBufAllocator[5]
             524288 |                  0 |       2048 | memory/ioBufAllocator[4]
                  0 |                  0 |       1024 | memory/ioBufAllocator[3]
                  0 |                  0 |        512 | memory/ioBufAllocator[2]
              32768 |                  0 |        256 | memory/ioBufAllocator[1]
                  0 |                  0 |        128 | memory/ioBufAllocator[0]
            2138112 |            2124192 |        928 | memory/cacheVConnection

[~bcall] has observed this issue on 4.0.x, and we have observed this on 4.2.x.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to