commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Vandahl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCS-177) CompositeCacheManager leaks memory if CacheAccess.dipose is called
Date Wed, 14 Jun 2017 16:50:00 GMT

    [ https://issues.apache.org/jira/browse/JCS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049366#comment-16049366
] 

Thomas Vandahl commented on JCS-177:
------------------------------------

Thank you for the bug report and your patch. I however took a different approach to fix the
problem using freeCache(). See commit 1798715. Please note that calling manager.release()
will dispose all your caches which is probably not what you want.

> CompositeCacheManager leaks memory if CacheAccess.dipose is called
> ------------------------------------------------------------------
>
>                 Key: JCS-177
>                 URL: https://issues.apache.org/jira/browse/JCS-177
>             Project: Commons JCS
>          Issue Type: Bug
>          Components: Composite Cache
>    Affects Versions: jcs-2.1
>            Reporter: Ryan Fong
>            Priority: Critical
>             Fix For: jcs-2.2
>
>         Attachments: jcs-177.patch, jcs-test.zip
>
>
> In JCS 2.1, The org.apache.commons.jcs.engine.control.CompositeCacheManager holds onto
a reference of CacheAccess in its caches map. If CacheAccess.dispose is called, this reference
is not cleaned up which results in a memory leak.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message