I tested once more our code in order to check the memory leaks.
Here is the list of leaking test suites:
- testatomicupdates
- testindexreader
- testanalyzers
- testRAMDirectory
- testindexwriter
- testIndexModifier
- testAddIndexesNoOptimize
- testsearch
- testRangeFilter
- testConstantScoreQueries
- testsort
- testdatefilter
- testutf8
- testBitSet
- testExtractTerms
Something must have changed in the code during the merges because I am sure
that at least the testExtractTerms test didn't produce memory leaks.
Let us get rid of the leaks! I will start from the bottom
with the testExtractTerms test. Should we create a new branch for this issue?
Jiri
-----Original Message-----
From: Veit Jahns [mailto:nuncupa...@googlemail.com]
Sent: Sunday, September 19, 2010 9:51 PM
To: clucene-developers@lists.sourceforge.net
Subject: Re: [CLucene-dev] Current branches state
2010/9/16 Itamar Syn-Hershko <ita...@code972.com>:
> Veit, Borek and Jiri - please have a look at master and make sure the
> merge did not ruin your changes (this sometimes happens), and that I
> resolved all merge conflicts correctly. Once you confirmed the merge,
> please test the branch as intensively as possible. After you have done
> this, please remove your merged branches from the repo.
Compiles and runs on FreeBSD as well as Win7/VS2010. But the one of
the tests for my StringBuffer extension failed. Fixed it. I needed
this extension for the GermanAnalyzer. But I havn't completed the port
yet, so the merge of veit_working into master was may be a little bit
early. But as this is a contrib no harm will be done to the core.
> From now on, everyone with a repo access bit, please have a branch per
> feature / fix and make sure it doesn't become stale until it is accepted
> and merged to master. I'll do my best to merge features and fixes as
> quickly as possible - having one branch per change is going to make this
> simpler anyway.
But in the case of the failing StringBuffer tests mentioned above I
pushed the commits directly to the master branch (sorry). The remaing
ported code for the GermanAnalyzer will be pushed to a separate
branch.
Borek/Jiří, one of you mentioned, that there observed memory leaks in
tests. Are they still there? I ask, because veit_working had many
memory leak fixes.
Veit
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
CLucene-developers mailing list
CLucene-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clucene-developers
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
CLucene-developers mailing list
CLucene-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clucene-developers
