Borek, a quick update: Apparently I was wrong. The 2 issues mentioned in JIRA 1072 were already fixed in 2.3.2, and the core patches attached to it weren't showing up in the release since other check-ins updated them to work differently.
So, what you were experiencing is either a CLucene specific bug or some JLucene behavior that isn't tolerated properly in a non-GC environment. Another option is that some code portion hasn't been ported in full, or correctly. I think it is better at this point to investigate where CLucene is failing JL tests and why, and then try to fix this accordingly (instead of tracking loads of memory allocations until you pinpoint the issue you are having and create a test case out of it). testWickedLongTerm (which I ported) is failing in one of the asserts - I think it is worth a look. Another test I think can help is testDocumentsWriterAbort (which I haven't ported yet). Other than that, trying to compare CLucene code files with their parallel Java's, and port more tests which test relevant code portions is also a good idea. Please update your local copy of the master branch, I have checked-in some more updates and tests. I also updated the test suite so it is somewhat easier to port Java tests into it. Let me know how it goes, I'll try to do some more work on this later this week. Itamar. On 25/6/2010 4:06 PM, Kostka Bořivoj wrote: > OK, I'm going to port this. > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ CLucene-developers mailing list CLucene-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/clucene-developers
