[jira] [Commented] (TS-3257) possible memory leak in v5.2.0

["Bryan Call (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255975#comment-14255975 ] 

Bryan Call commented on TS-3257:
--------------------------------


Turned on proxy.config.res_track_memory on the server and monitoring.

So far:
{code}
                                          Location |          Size In-use
---------------------------------------------------+------------------------
                      memory/IOBuffer/FetchSM.h:61 |                77824
                      memory/IOBuffer/FetchSM.h:63 |                98304
               memory/IOBuffer/InkIOCoreAPI.cc:499 |             27082752
                  memory/IOBuffer/PluginVC.cc:1007 |                98304
                  memory/IOBuffer/PluginVC.cc:1010 |                    0
  memory/IOBuffer/ProtocolProbeSessionAccept.cc:67 |             51740672
          memory/IOBuffer/HttpClientSession.cc:199 |              1196032
                    memory/IOBuffer/HttpSM.cc:5402 |                    0
                    memory/IOBuffer/HttpSM.cc:5730 |                    0
                    memory/IOBuffer/HttpSM.cc:5821 |                57344
                    memory/IOBuffer/HttpSM.cc:6021 |                    0
                    memory/IOBuffer/HttpSM.cc:6282 |                    0
                    memory/IOBuffer/HttpSM.cc:6318 |               110592
           memory/IOBuffer/HttpServerSession.cc:87 |              1073152
                 memory/IOBuffer/HttpTunnel.cc:100 |                  512
                     memory/IOBuffer/Cache.cc:2735 |              1298432
                     memory/IOBuffer/Cache.cc:2749 |           1012367360
         memory/IOBuffer/P_SSLNetVConnection.h:153 |              8900608
                                             TOTAL |           1104101888
{code}

> possible memory leak in v5.2.0
> ------------------------------
>
>                 Key: TS-3257
>                 URL: https://issues.apache.org/jira/browse/TS-3257
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 5.2.0
>            Reporter: Sudheer Vinukonda
>             Fix For: 5.3.0
>
>
> After running v5.2.0 over the weekend on one of our prod hosts, I've noticed that the RES memory from top grew to 21g (the corresponding RES memory on a v5.0 prod host is 10g). Looking at the memory dump, it seems that it might be leaking 4K iobuffers. The memory dump shows as much as 10g of 4K buffers allocated/in-use (on the corresponding v5 host, the 4k buffers are only at 300MB level)
> {code}
> -bash-4.1$ sudo grep "memory/ioBufAllocator\[5\]" traffic.out 
>          9421979648 |         9421180928 |       4096 | memory/ioBufAllocator[5]
>          9431416832 |         9429147648 |       4096 | memory/ioBufAllocator[5]
>          9700900864 |         9692045312 |       4096 | memory/ioBufAllocator[5]
> {code}



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