Can you send a simple test case showing the bug? DIGY
-----Original Message----- From: Floyd Wu [mailto:[EMAIL PROTECTED] Sent: Friday, October 10, 2008 7:46 PM To: lucene-net-user@incubator.apache.org Subject: Re: Huge memory usage Hi Digy I've applied the patched you provided and still got this problem, which is using lots memory. It seems that after applying patch, memory uasge got improvement. Proved by profiler, I;m sure that I still got memory leakage and probably come from SegmentReader and caused FieldInfo object instance increased. Thanks for your reply and help. 2008/10/9 Digy <[EMAIL PROTECTED]> > Can you try the patch LUCENENET-106 "Paches for v2.3.1.rar"? > It contains 3 patches and a new class "WeakHashTable". > > There is also another patch (WeakHashTable+FieldCacheImpl.rar) for > Lucene.Net 2.1 > > DIGY > > -----Original Message----- > From: Floyd Wu [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 09, 2008 5:00 AM > To: lucene-net-user@incubator.apache.org > Subject: Huge memory usage > > Hi all, > It seems that issue, > http://issues.apache.org/jira/browse/LUCENENET-106still > > not being fully fixed. > My observation of memory usage still getting increasing. > > By using two profilers(YourKits profiler and MS .Net CLR Profiler), I found > that "Lucene.Net.Index.SegmentReader/Norm" and "Lucene.Net.Index.FieldInfo" > > will be increased 41 object(both these two classes) instances when > searching > > index(yes, sort is involved). > > These increased object instances won't be grabage-collected and as result > my > system will soon reached memory limitation and fire CLR recycle whole > process. > My Lucene.Net version is 2.3.1.2 and source is grab from SVN. > Please help on this. > Best regards, > Floyd > >
