commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Fong (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCS-177) CompositeCacheManager leaks memory if CacheAccess.dipose is called
Date Thu, 04 May 2017 16:24:04 GMT

     [ https://issues.apache.org/jira/browse/JCS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ryan Fong updated JCS-177:
--------------------------
    Attachment: jcs-test.zip
                jcs-177.patch

I have attached one possible solution that should fix this problem as jcs-177.patch. An alternative
to this is to have a pointer from CompositeCache to CompositeCacheManager so we do not incur
the overhead of incrementing and decrementing the client count.

Also find an Eclipse project that uses stock 2.1 to demonstrate how the leak occurs and how
CompositeCacheManager.freeCache avoids this issue.

> 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
>    Affects Versions: jcs-2.1
>            Reporter: Ryan Fong
>            Priority: Critical
>         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.3.15#6346)

Mime
View raw message