You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2014/12/23 17:57:17 UTC
[jira] [Resolved] (TS-3257) possible memory leak in v5.2.0
[ https://issues.apache.org/jira/browse/TS-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom resolved TS-3257.
-------------------------------
Resolution: Fixed
> 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
> Assignee: Sudheer Vinukonda
> Priority: Blocker
> Fix For: 5.2.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)