some other memory leak in your application.
-Original Message-
From: Fernando Padilla [mailto:[EMAIL PROTECTED]
Sent: Friday, May 12, 2006 1:35 PM
To: java-dev@lucene.apache.org
Subject: Re: LUCENE-436
hmm. So what you're saying is that there is a "memory leak", but very
v
Sent: Thursday, May 11, 2006 9:53 PM
To: java-dev@lucene.apache.org
Subject: Re: LUCENE-436
so... what do you think?
We just took the patch through QA and there was a noticeable memory
increase through time, and once we applied the patch, the memory didn't
increase..
So if you don'
, RAMDirectories are either broken, or everyone takes a performance hit.
-Original Message-
From: Fernando Padilla [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 11, 2006 9:53 PM
To: java-dev@lucene.apache.org
Subject: Re: LUCENE-436
so... what do you think?
We just took the patch through QA and
so... what do you think?
We just took the patch through QA and there was a noticeable memory
increase through time, and once we applied the patch, the memory didn't
increase..
So if you don't like the solution.. what are some alternatives?
fernando
ps - www.protrade.com
Otis Gospodnetic w
