It's entirely possible that you are seeing a different leak.
Can you turn on proxy.config.res_track_memory and share the output?
Please also open a jira with the relevant details.
Thanks,
Sudheer
From: "Eagen, Dave" <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Monday, February 23, 2015 6:16 AM
Subject: TS-3257 not fixed yet?
<!--#yiv4510318796 _filtered #yiv4510318796 {font-family:Helvetica;panose-1:2
11 6 4 2 2 2 2 2 4;} _filtered #yiv4510318796 {font-family:Helvetica;panose-1:2
11 6 4 2 2 2 2 2 4;} _filtered #yiv4510318796 {font-family:Calibri;panose-1:2
15 5 2 2 2 4 3 2 4;} _filtered #yiv4510318796 {font-family:"Helvetica
Light";}#yiv4510318796 #yiv4510318796 p.yiv4510318796MsoNormal, #yiv4510318796
li.yiv4510318796MsoNormal, #yiv4510318796 div.yiv4510318796MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri",
"sans-serif";}#yiv4510318796 a:link, #yiv4510318796
span.yiv4510318796MsoHyperlink
{color:blue;text-decoration:underline;}#yiv4510318796 a:visited, #yiv4510318796
span.yiv4510318796MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv4510318796
span.yiv4510318796EmailStyle17 {font-family:"Calibri",
"sans-serif";color:windowtext;}#yiv4510318796 .yiv4510318796MsoChpDefault
{font-family:"Calibri", "sans-serif";} _filtered #yiv4510318796 {margin:1.0in
1.0in 1.0in 1.0in;}#yiv4510318796 div.yiv4510318796WordSection1 {}-->We seem to
have been hitting TS-3257 even though it was supposed to be fixed in 5.2.0
according tohttps://issues.apache.org/jira/browse/TS-3257. We then tried going
to git head on the 12th [Apache Traffic Server - traffic_line - 5.3.0 - (build
# 021209 on Feb 12 2015 at 09:07:08)] but are still experiencing apparently
unbounded growth in ioBufAllocator[5]. Here is what traffic.out showed this
morning before and after restarting: 7024934912 | 7023685632 |
4096 | memory/ioBufAllocator[5] 7024934912 | 7023505408 | 4096 |
memory/ioBufAllocator[5] 7024934912 | 7023542272 | 4096 |
memory/ioBufAllocator[5] 7864320 | 7831552 | 4096 |
memory/ioBufAllocator[5] 12058624 | 11972608 | 4096 |
memory/ioBufAllocator[5] 14680064 | 14299136 | 4096 |
memory/ioBufAllocator[5] 16252928 | 16027648 | 4096 |
memory/ioBufAllocator[5] 17825792 | 17514496 | 4096 |
memory/ioBufAllocator[5] Is 3257 really not fixed yet or are we experiencing
a different leak? DAVID EAGEN
This e-mail message is being sent solely for use by the intended recipient(s)
and may contain confidential information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by phone or reply by e-mail, delete the
original message and destroy all copies. Thank you.
