[
https://issues.apache.org/jira/browse/LUCENE-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723276#action_12723276
]
Michael McCandless commented on LUCENE-1715:
--------------------------------------------
I agree nulling is not a good practice to make GC faster.
But... for freeing up memory even if the app still holds a reference to the
reader after closing it, I think this is in fact worthwhile.
> DirectoryIndexReader finalize() holding TermInfosReader longer than necessary
> -----------------------------------------------------------------------------
>
> Key: LUCENE-1715
> URL: https://issues.apache.org/jira/browse/LUCENE-1715
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Affects Versions: 2.4.1
> Environment: Sun JDK 6 update 12 64-bit, Debian Lenny
> Reporter: Brian Groose
> Assignee: Michael McCandless
> Fix For: 2.9
>
>
> DirectoryIndexReader has a finalize method, which causes the JDK to keep a
> reference to the object until it can be finalized. SegmentReader and
> MultiSegmentReader are subclasses that contain references to, potentially,
> hundreds of megabytes of cached data in a TermInfosReader.
> Some options would be removing finalize() from DirectoryIndexReader (it
> releases a write lock at the moment) or possibly nulling out references in
> various close() and doClose() methods throughout the class hierarchy so that
> the finalizable object doesn't references the Term arrays.
> Original mailing list message:
> http://mail-archives.apache.org/mod_mbox/lucene-java-user/200906.mbox/%[email protected]%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
