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" <David.Eagen@biworldwide.com>
To: "users@trafficserver.apache.org" <users@trafficserver.apache.org>
Sent: Monday, February 23, 2015 6:16 AM
Subject: TS-3257 not fixed yet?

We seem to have been hitting TS-3257 even though it was supposed to be fixed in 5.2.0 according to https://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.