Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=ix.netcom.com;
  b=XOdpmIivqBazG2XrlOG2mjEhimji3reNe/8CpsQkhjkWRVGqFH1+tLY1z1ofz9h6;
  h=Received:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <16299949.1152320430179.JavaMail.jira@brutus>
References: <16299949.1152320430179.JavaMail.jira@brutus>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <09C43B08-3EEE-49F0-9A90-379483D5BF06@ix.netcom.com>
Content-Transfer-Encoding: 7bit
From: robert engels <rengels@ix.netcom.com>
Subject: Re: [jira] Commented: (LUCENE-623) RAMDirectory.close() should have a
 comment about not releasing any resources
Date: Fri, 7 Jul 2006 20:39:02 -0500
To: java-dev@lucene.apache.org

I don't think there is any leak at all. the problem was the caller  
was maintaining a reference to the reader after close was called  
(which prevents usage anyway), and wanted to free some of the  
underlying memory - kind of pointless, he should just release the ref  
to the IndexReader (since it is unusable anyway).

The patch was not needed.

On Jul 7, 2006, at 8:00 PM, Yonik Seeley (JIRA) wrote:

>     [ http://issues.apache.org/jira/browse/LUCENE-623? 
> page=comments#action_12419805 ]
>
> Yonik Seeley commented on LUCENE-623:
> -------------------------------------
>
> Just out of curiousity, does Lucene hold onto a RAMDirectory  
> instance somewhere after it has called close on it?  If so, that  
> would have been the ideal place to fix it any kind of "leak".
>
> This patch, while not doing much harm, is not really "best  
> practice" in Java and the existing RAMDirectory close() was correct.
> Am I missing something?
>
>> RAMDirectory.close() should have a comment about not releasing any  
>> resources
>> --------------------------------------------------------------------- 
>> -------
>>
>>          Key: LUCENE-623
>>          URL: http://issues.apache.org/jira/browse/LUCENE-623
>>      Project: Lucene - Java
>>         Type: Improvement
>
>>   Components: Store
>>     Versions: 1.9
>>     Reporter: Heng Mei
>>     Assignee: Hoss Man
>>     Priority: Minor
>>  Attachments: ramdirectory.diff
>>
>> I wrongly assumed that calling RAMDirectory.close() would free up  
>> the memory occupied by the RAMDirectory.
>> It might be helpful to add a javadoc comment that warns users that  
>> RAMDirectory.close() is a no-op, since it might be a common  
>> assumption that close() would release resources.
>
> -- 
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the  
> administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
>    http://www.atlassian.com/software/jira
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org