Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: domain of erickerickson@gmail.com
 designates 64.233.166.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=tDoRnhENN1y1UR+mTvPhlp2OZ+wzvN8kqk4CuCJFRptRZuiOPLdIGR6kUcxfwG/dpuuJvGWFsNqzlCiN7PdThqVMXLYDD/z8ndkLICj8khlXmqH4TrxpNYXdBvxHovQcN5oizI54iTRFSges+Ol8KmOC15oseDibmRXxZwrYTN4=
Message-ID: <359a92830607031029m3a44fb4fo33313651c76f0aa5@mail.gmail.com>
Date: Mon, 3 Jul 2006 13:29:31 -0400
From: "Erick Erickson" <erickerickson@gmail.com>
To: java-user@lucene.apache.org
Subject: Re: Memory Leak IndexSearcher
In-Reply-To: <9cde41450607030742jb64b0c0p71d4732ba5bc132c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_17223_16689495.1151947771573"
References: <9cde41450607030742jb64b0c0p71d4732ba5bc132c@mail.gmail.com>

------=_Part_17223_16689495.1151947771573
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Well, *assuming* that you're working in Java, you can't predict very much
about when the garbage collector actually goes about freeing memory.
Depending on how memory is measured, you may or may not be getting an
accurate count.

I wonder what would happen if you allowed the JVM only a *little* more
memory than you need. I suspect that you'd see memory increase to the
maximum then fluctuate near the max forever as the gc would then be forced
to collect the memory that was being marked as free (but not necessarily
returned to the heap by the GC promptly) by re-opening the IndexSearcher.

Hope this helps
Erick

------=_Part_17223_16689495.1151947771573--