[
https://issues.apache.org/jira/browse/TS-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256307#comment-14256307
]
Sudheer Vinukonda commented on TS-3257:
---------------------------------------
The iobuffers seemed stable after the fix, but, traffic_server somehow still
ended up hogging a lot of memory (21g RES memory on a 24g RAM system) and
became unresponsive. I am not sure if it's because of keeping the memory
tracking enabled. I've turned it off, restarted the host. Will monitor and
update.
> 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
> Priority: Blocker
> 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)
