[ https://issues.apache.org/jira/browse/TS-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001990#comment-14001990 ]
Bryan Call commented on TS-2098: -------------------------------- [~klindgren] Can you please reply to James comment or we will close the bug because we can't reproduce > 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 > Assignee: James Peach > Priority: Blocker > Fix For: 5.0.0 > > Attachments: assert.diff > > > 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 was sent by Atlassian JIRA (v6.2#6252)