[
https://issues.apache.org/jira/browse/TS-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256106#comment-14256106
]
Sudheer Vinukonda commented on TS-3257:
---------------------------------------
With the above patch, the memory looks stable so far (although, need to monitor
more):
{code}
-bash-4.1$ sudo grep "memory/ioBufAllocator\[5\]" traffic.out
0 | 0 | 4096 | memory/ioBufAllocator[5]
27262976 | 26992640 | 4096 | memory/ioBufAllocator[5]
48234496 | 45158400 | 4096 | memory/ioBufAllocator[5]
70778880 | 70471680 | 4096 | memory/ioBufAllocator[5]
116916224 | 115650560 | 4096 | memory/ioBufAllocator[5]
124780544 | 123838464 | 4096 | memory/ioBufAllocator[5]
124780544 | 123768832 | 4096 | memory/ioBufAllocator[5]
124780544 | 122884096 | 4096 | memory/ioBufAllocator[5]
128974848 | 127803392 | 4096 | memory/ioBufAllocator[5]
152043520 | 133128192 | 4096 | memory/ioBufAllocator[5]
152043520 | 133406720 | 4096 | memory/ioBufAllocator[5]
152043520 | 130859008 | 4096 | memory/ioBufAllocator[5]
152043520 | 132739072 | 4096 | memory/ioBufAllocator[5]
152043520 | 133054464 | 4096 | memory/ioBufAllocator[5]
152043520 | 129527808 | 4096 | memory/ioBufAllocator[5]
152043520 | 131260416 | 4096 | memory/ioBufAllocator[5]
152043520 | 130875392 | 4096 | memory/ioBufAllocator[5]
{code}
{code}
-bash-4.1$ sudo grep "P_SSLNetVConnection.h" traffic.out
memory/IOBuffer/P_SSLNetVConnection.h:153 | 802816
memory/IOBuffer/P_SSLNetVConnection.h:153 | 1097728
memory/IOBuffer/P_SSLNetVConnection.h:153 | 1679360
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4730880
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4628480
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4632576
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4591616
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4628480
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4915200
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4825088
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4780032
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4902912
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4874240
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4894720
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4775936
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4485120
memory/IOBuffer/P_SSLNetVConnection.h:153 | 4792320
-bash-4.1$
{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)
