[
https://issues.apache.org/jira/browse/TS-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734160#comment-13734160
]
James Peach commented on TS-2098:
---------------------------------
I think that this is a reference counting problem. The SSL certificate loader
uses ConfigInfo which is reference counted, but when ConfigProcessor::release()
looks at it, there are outstanding references and the object is never deleted.
Interestingly, this doesn't show up as a memory leak in standard tools, so
there might be a reference (circular?) to that somewhere.
> Memory leak with reloading SSL certificates 3.3.4
> -------------------------------------------------
>
> Key: TS-2098
> URL: https://issues.apache.org/jira/browse/TS-2098
> Project: Traffic Server
> Issue Type: Bug
> Components: SSL
> Affects Versions: 3.3.4
> Reporter: Kris Lindgren
> Fix For: 3.3.6
>
>
> When using the new feature of 3.3.4 to re-read the ssl configuration without
> restart the old memory that the configuration uses is not released.
> I have ~220k ssl certs defined which consumes ~1.2gb of memory. If I
> add/remove a single ssl cert from ssl_multicert.config and reload via
> traffic_line -x memory usage increases from 1.2gb to 2.4gb and stays there.
> If I make another change and reload again via traffic_line -x, memory usage
> jumps to 3.6gb and stays there.
> It appears that after successfully loading the new configuration into memory
> the old configuration is never purged.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
