lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Digy (JIRA)" <>
Subject [jira] Closed: (LUCENENET-191) Memory Leak Lucene.Net-
Date Wed, 14 Oct 2009 17:06:31 GMT


Digy closed LUCENENET-191.

    Resolution: Invalid
      Assignee: Digy

Hi Ashish,

After one month without any concrete testcase, I am closing this issue. 
Feel free to reopen this issue, if you are sure that there is a really a memory leakage.


> Memory Leak Lucene.Net-
> ------------------------------
>                 Key: LUCENENET-191
>                 URL:
>             Project: Lucene.Net
>          Issue Type: Bug
>         Environment: Operating System: Microsoft Windows XP Professional version 2002,
Service Pack 2
> Software platform: Visual studio .Net 2008, Framework-3.5
>            Reporter: Ashish Kr Dey
>            Assignee: Digy
>   Original Estimate: 96h
>  Remaining Estimate: 96h
> I am using Lucene.Net- in my project. My project also supporting multithreading
environment. Lucene Indexing service is working as Windows Service. Problem is when the service
is running, it's memory blockage is gradually increasing. So after some hours, it shows a
memory of 150 mb in Task Manager where as it start with 13 it has a memory increasing
behavior. I identified by dotTrace Profiler that in Lucene.Net there are some methods and
objects that increased the memory. From Call Tree one of my dotTrace out put  identify that
Index(), Segment() related functions hold's memory increased as long as the service perform.
So it at a time, it will crash the system.
> Please help me how i can recover my application from this memory leakage. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message