lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Svensson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENENET-537) Memory leak while indexing more than 500.000 documents.
Date Mon, 24 Feb 2014 15:13:19 GMT

    [ https://issues.apache.org/jira/browse/LUCENENET-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910387#comment-13910387
] 

Simon Svensson commented on LUCENENET-537:
------------------------------------------

Hi,

An OutOfMemoryException doesn't really mean that you're out of memory, just that the runtime
failed to find a continuous memory area large enough when requested.

You don't happen to have a stack-trace or memory/process dump when this happens? It would
help alot in pinpointing what's wrong. Are you using a 32-bit or 64-bit machine? Perhaps a
32-bit process in a 64-bit environment? Do you have a lot of free memory, according to Task
Manager, when this occurs?

// Simon

> Memory leak while indexing more than 500.000 documents.
> -------------------------------------------------------
>
>                 Key: LUCENENET-537
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-537
>             Project: Lucene.Net
>          Issue Type: Bug
>          Components: Lucene.Net Core
>    Affects Versions: Lucene.Net 3.0.3
>         Environment: IIS
>            Reporter: Jörg Hubacher
>            Priority: Blocker
>
> When I'm reindexing a hudge number of documents I've getting an out of memory exception
after some hours.
>                 using (IndexWriter writer = this.CreateIndexWriter(_directory))
>                 {
>                     writer.DeleteAll();
>                     foreach (Product product in _service.GetAllProducts())
>                     {
>                         Document doc = CreateDocument(product);
>                         writer.AddDocument(doc);
>                     }
>                     writer.Commit();
>                     writer.Optimize();
>                 }
> This came up with version 3.0.3. Before it was ok.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message