You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by bu...@apache.org on 2004/08/12 20:43:19 UTC

DO NOT REPLY [Bug 30628] New: - Possible Memory leak in Sort

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

           Summary: Possible Memory leak in Sort
           Product: Lucene
           Version: 1.4
          Platform: PC
               URL: http://http://
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Analysis
        AssignedTo: lucene-dev@jakarta.apache.org
        ReportedBy: john@rte.ie


Lucene 1.4.1
Tomcat 5.0.27
SDK's IBM 1.4.2, and Sun 1.4.2_05-b04
OS Fedora Core2

Using the sort feature within my search application quickly uses up the 1000MB
Java Heap I have assigned to Tomcat 5.0.27 and kills the server.
hits = searcher.search(query,new Sort(new SortField("byNumber",3)));


Not sorting works fine

Happens: always


John

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