[
https://issues.apache.org/jira/browse/LUCENENET-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erich Eichinger updated LUCENENET-106:
--------------------------------------
Attachment: WeakReferences.rar
It seems this bug has been reintroduced from r1.4.3 - see my mails to the
lucene-net list here:
http://mail-archives.apache.org/mod_mbox/incubator-lucene-net-dev/200704.mbox/[EMAIL
PROTECTED]
http://markmail.org/message/tilrugo4kux2yysq
http://markmail.org/message/nv4l346tecrkpwgx
http://www.mail-archive.com/[EMAIL PROTECTED]/msg00392.html
I attached an implementation of WeakHashtable that I've done exactly to fix
those memory leaks. It is based on NHibernate's WeakHashtable implementation so
they might want to get some credits.
hope this helps
> Lucene.NET (Revision: 603121) is leaking memory
> -----------------------------------------------
>
> Key: LUCENENET-106
> URL: https://issues.apache.org/jira/browse/LUCENENET-106
> Project: Lucene.Net
> Issue Type: Bug
> Environment: .NET 2.0
> Reporter: Anton K.
> Priority: Critical
> Attachments: DIGY-FieldCacheImpl.patch, Digy.rar,
> luceneSrc_memUsage.patch, WeakReferences.rar
>
>
> 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.
> http://www.gossamer-threads.com/lists/lucene/java-user/55681
> 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.
