lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregor Kaczor (JIRA)" <j...@apache.org>
Subject [jira] Created: (LUCENE-2328) IndexWriter.synced field accumulates data leading to a Memory Leak
Date Wed, 17 Mar 2010 20:15:30 GMT
IndexWriter.synced  field accumulates data leading to a Memory Leak
-------------------------------------------------------------------

                 Key: LUCENE-2328
                 URL: https://issues.apache.org/jira/browse/LUCENE-2328
             Project: Lucene - Java
          Issue Type: Bug
          Components: Index
    Affects Versions: 3.0.1, 3.0, 2.9.2, 2.9.1
         Environment: all
            Reporter: Gregor Kaczor
            Priority: Minor


I am running into a strange OutOfMemoryError. My small test application does
index and delete some few files. This is repeated for 60k times. Optimization
is run from every 2k times a file is indexed. Index size is 50KB. I did analyze
the HeapDumpFile and realized that IndexWriter.synced field occupied more than
half of the heap. That field is a private HashSet without a getter. Its task is
to hold files which have been synced already.

There are two calls to addAll and one call to add on synced but no remove or
clear throughout the lifecycle of the IndexWriter instance.

According to the Eclipse Memory Analyzer synced contains 32618 entries which
look like file names "_e065_1.del" or "_e067.cfs"

The index directory contains 10 files only.

I guess synced is holding obsolete data 

-- 
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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message