Do you know how big the documents are that you are trying to delete/update? I'm trying to find a copy of 2.9.2 to see if I can reproduce it.
Thanks, Christopher On Tue, Nov 29, 2011 at 9:11 AM, Trevor Watson < [email protected]> wrote: > Sorry for the duplicate post. I was on the road and posted both via my web > mail and office mail by mistake > > The increase is a very gradual, the program starts at about 160,000k > according to task manager (I know that's not entirely accurate, but it was > the best I had at the time) and would, after adding 25,000-40,000 result in > an out of memory exception (800,000k according to taskmanager). I tried > building a copy of 2.9.4 to test, but could not find one that worked in > visual studio 2005 > > I did notice using Ants memory profiler that there were a number of > byte[32789] arrays that I didn't know where they came from in memory. > > On Monday, November 28, 2011, Christopher Currens <[email protected] > > > wrote: > > Hi Trevor, > > > > What kind of memory increase are we talking about? Also, how big are the > > documents that you are indexing, the ones returned from getFileInfoDoc()? > > Is it putting an entire file into the index? Pre 2.9.3 versions had > > issues with holding onto allocated byte arrays far beyond when they were > > used. The memory could only be freed via closing the IndexWriter. > > > > I'm a little unclear on exactly what's happening. Are you noticing > memory > > spike and stay constant at that level or is it a gradual increase? Is it > > causing your application to error, (ie OutOfMemory exception, etc)? > > > > > > Thanks, > > Christopher > > > > On Mon, Nov 28, 2011 at 5:59 PM, Trevor Watson < > > [email protected]> wrote: > > > >> I'm attempting to use Lucene.Net v2.9.2.2 in a Visual Studio 2005 (.NET > >> 2.0) environment. We had a piece of software that WAS working. I'm not > >> sure what has changed however, the following code results in a memory > leak > >> in the Lucene.Net component (or a failure to clean up used memory). > >> > >> The code in issue is here: > >> > >> private void SaveFileToFileInfo(Lucene.Net.Index.IndexWriter iw, bool > >> delayCommit, string sDataPath) > >> { > >> Document doc = getFileInfoDoc(sDataPath); > >> Analyzer analyzer = clsLuceneFunctions.getAnalyzer(); > >> if (this.FileID == 0) > >> { > >> string s = ""; > >> } > >> iw.UpdateDocument(new Lucene.Net.Index.Term("FileId", > >> this.fileID.ToString("000000000")), doc, analyzer); > >> > >> analyzer = null; > >> doc = null; > >> if (!delayCommit) > >> iw.Commit(); > >> } > >> > >> Commenting out the line iw.UpdateDocument resulted in no memory > increase. > >> I also tried replacing it with a deleteDocument and AddDocument and the > >> memory increased the same as using the UpdateDocument function > >> > >> The getAnalyzer() function returns a ExtendedStandardAnalyzer, but it's > the > >> UpdateDocument line specifically that gives me the issue. > >> > >> Any assistance would be greatly appreciated. > >> > >> Trevor Watson > >> > > >
