Mailing-List: contact lucene-net-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: lucene-net-user@incubator.apache.org
From: "George Aroush" <george@aroush.net>
To: <lucene-net-user@incubator.apache.org>,
	<lucene-net-dev@incubator.apache.org>
Subject: RE: Memory leak with sorted searches
Date: Thu, 28 Sep 2006 13:55:44 -0400
Message-ID: <001a01c6e327$53101370$ee6ffea9@aroushlt>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <e500e2940609271558r6e942585q20210e516f4d9939@mail.gmail.com>
Thread-Index: AcbiiGhNk5nDMD1NTNiaVPwoiE47AwAnW2og

Hi Phil and Michael,

I don't know about that proposed fix you referred to and I don't know if the
known memory leak, during indexing, in Lucene.Net 1.9, 1.9.1 and 2.0 is the
same leak as what you are observing with the sort.

To help me track this down, can you:

1) Try the fix that I found to fix a leak (see my earlier post.)
2) If #1 above doesn't fix your problem, try with .NET 2.0
3) If you are still seeing the problem, can you post an sample working code
which demonstrates the problem?

Regards,

-- George Aroush
 

-----Original Message-----
From: Philip Withington [mailto:philip.withington@gmail.com] 
Sent: Wednesday, September 27, 2006 6:58 PM
To: lucene-net-user@incubator.apache.org
Subject: Re: Memory leak with sorted searches

I am using .Net 1.1.  I found some proposed fixes to the problem here
http://blog.dotlucene.net/2006/06/lucenenet-19-rc1-build-003.html but would
rather not take the risk of modifying code I do not fully understand.  From
what I understand from reading the lists, the next release of Lucene.Net (
2.0) will initially be geared towards the 1.1 version of the framework so I
wonder if this will fix the problem.

Michael

Sorry if I've misunderstood but are you talking about re-sorting the hits
after you've initially retrieved them ordered by relevance?

Regards

Phil


On 9/27/06, Michael Mitiaguin <mitiaguin@gmail.com> wrote:
>
> Philip,
>
> Personally, I found feature a very slow ( comparing to search itself ) 
> , so I just sort memory collection after iterating Hits.
> You may have noticed messages regarding memory leak for indexing in 
> .Net
> 1.1
> Are you using .Net 1.1  ? I don't remember any memory leak when I used 
> it witn .Net 2
>
> Regards
> Michael
>
> On 9/28/06, Philip Withington <philip.withington@gmail.com> wrote:
> >
> > I'm finding that the memory leak problem with sorted searches means 
> > that
> I
> > cannot use this feature of Lucene.Net.  I'm using version 1.9.1.  Is
> there
> > a
> > version out there with a fix for this problem or will it be fixed in 
> > a forthcoming release?
> >
> > Regards
> >
> > Phil
> >
> >
>
>