lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Digy (JIRA)" <>
Subject [jira] Commented: (LUCENENET-106) Lucene.NET (Revision: 603121) is leaking memory
Date Sat, 05 Jan 2008 17:24:34 GMT


Digy commented on LUCENENET-106:

Since "readerCache" in "FieldCacheImpl.Cache.Get()"  stores a reference to IndexReaders, IndexReaders
are never garbage-collected.
Instead of using the IndexReader itself,using the HashCode of it as key allows it to get garbage-collected.
This change eliminates most of the memory leakage. 
But still the entry of the garbage-collected IndexReader remains in readerCache. This is the
second reason of the memory leakage.
I will send another patch that utilizes WeakReference to determine whether an IndexReader
is garbage-collected or not. If Yes,then the entry in readerCache can safely be removed. 
This patch(DIGY-FieldCacheImpl.patch) does not require a change in IndexReader class.

> Lucene.NET (Revision: 603121) is leaking memory
> -----------------------------------------------
>                 Key: LUCENENET-106
>                 URL:
>             Project: Lucene.Net
>          Issue Type: Bug
>         Environment: .NET 2.0
>            Reporter: Anton K.
>            Priority: Critical
>         Attachments: DIGY-FieldCacheImpl.patch, Digy.rar, luceneSrc_memUsage.patch
> readerCache Hashtable field (see FieldCacheImpl.cs) never releases some hash items that
have closed IndexReader object as a key. So a lot of Term instances are never released.
> Java version of Lucene uses WeakHashMap and therefore doesn't have this problem.
> This bug can be reproduced only when Sort functionality used during search. 
> See following link for additional information.
> Steps to reproduce:
> 1)Create index
> 2) Modify index by IndexWiter; Close IndexWriter
> 3) Use IndexSearcher for searching with Sort; Close InexSearcher
> 4) Go to step 2
> You'll get OutOfMemoryException after some time of running this algorithm.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message