DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30628>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30628 Possible Memory leak in Sort [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2004-08-13 21:08 ------- That code looks wrong. You are creating your IndexSearcher inside a for loop, which results in 500 instances of IndexSearcher. That is not what you wanted to do, is it? You should re-use the IndexSearcher for the same index. Yes, you do close your IndexSearcher, but as Daniel pointed out, that too looks suspicious, as you close that inside an inner for loop. Because of this, I'll mark this bug as invalid. However, there were some issues with Sort in Lucene 1.4 (yes, you are using 1.4.1), so please re-open if you find that you run out of memory even when you re-use IndexSearcher. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
