You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Gethin James (JIRA)" <ji...@apache.org> on 2016/08/11 09:13:20 UTC

[jira] [Commented] (SOLR-9406) SolrSuggester memory leak

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

Gethin James commented on SOLR-9406:
------------------------------------

A potential solution would be to put the following around the closehook creation:
{code}if (lookup != null && lookup instanceof Closeable) {
}{code}

> SolrSuggester memory leak
> -------------------------
>
>                 Key: SOLR-9406
>                 URL: https://issues.apache.org/jira/browse/SOLR-9406
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Suggester
>    Affects Versions: 4.10.3
>            Reporter: Gethin James
>            Assignee: Joel Bernstein
>
> SolrSuggester init method register a CloseHook keeping a reference to LookupFactory.
> If init() is called multiple times then multiple close hooks are added.  These are kept in memory and not reclaimed.
> See https://issues.alfresco.com/jira/browse/ACE-5148



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org