You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2010/03/06 22:14:27 UTC
[jira] Updated: (SOLR-1798) Memory leak in FastLRUCache
[ https://issues.apache.org/jira/browse/SOLR-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yonik Seeley updated SOLR-1798:
-------------------------------
Attachment: SOLR-1798.patch
I think the fix is as simple as this patch.
Verifying that it fixes it is slightly harder - I'll try breaking out the profiler.
> Memory leak in FastLRUCache
> ---------------------------
>
> Key: SOLR-1798
> URL: https://issues.apache.org/jira/browse/SOLR-1798
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.4, 1.5
> Reporter: Laxman
> Assignee: Yonik Seeley
> Fix For: 1.5
>
> Attachments: SOLR-1798.patch
>
>
> Every time a commit happens two Stats instances [org.apache.solr.common.util.ConcurrentLRUCache.Stats] are leaking.
> Following code [org.apache.solr.search.FastLRUCache] to maintain cumulative cache statistics causing this Stats object leak.
> {noformat}
> cumulativeStats = (List<ConcurrentLRUCache.Stats>) persistence;
> cumulativeStats.add(cache.getStats());
> {noformat}
> Everytime a *commit* happens a new cache object is getting created and its stats is added to the list which is not released at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.