[
https://issues.apache.org/jira/browse/TS-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517836#comment-14517836
]
Leif Hedstrom commented on TS-3566:
-----------------------------------
Acácio reported a problem where he'd see dramatic memory leaks prior to
TS-3561. However, looking at the code, and trying to duplicate that issue,
neither me nor Sudheer was able to reproduce it. I'm cloning and keeping this
bug open for now, and hoping that Acácio can give more details on how exactly
he reproduced this problem.
The intent of the code was to only create / destroy BgFetchConfig objects (and
hence the mutex) when the configuration was reloaded. It clearly should not
create / destroy these objects on every request.
> Possible duplication of BgFetchConfig in background_fetch plugin
> ----------------------------------------------------------------
>
> Key: TS-3566
> URL: https://issues.apache.org/jira/browse/TS-3566
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
> Reporter: Leif Hedstrom
> Fix For: 6.0.0
>
>
> In at least background_fetch and cache_promote, we don't destroy the mutex on
> config destruction. This was intentional, since the API didn't use to exist,
> but now it does.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
