[Kinosearch] Possible memory leak when iterating over the results in KinoSearch

[Nils Grunwald]

Hello,

First thanks for KinoSearch, it is great to have a powerful indexing 
engine in Perl, and the new dev API is very easy to play with, 
especially when coming from Lucene. Here is a problem I've encountered 
with the development branch on rev 3939. When iterating over a hits 
collected from a large index, the memory is never released. In this 
small test case I get out of memory after a few iterations, and I see 
memory grow with each iteration of the loop. I think the problem lies in 
calling hits->next. Is there something I have not seen to do to 
explicitly destroy the objects, or do you need something else to help me 
find the problem ? Interestingly, the same thing was also leaking memory 
in the last build I used (rev 3892) but at a much slower pace. My test 
machine is a linux 2.6.22-14-server and it passes the test suite just fine.

Thanks for your help,

Nils Grunwald
-------------- next part --------------
A non-text attachment was scrubbed...
Name: minimal.pl
Type: application/x-perl
Size: 1151 bytes
Desc: not available
Url : http://rectangular.com/pipermail/kinosearch/attachments/20081209/7e354fae/attachment-0006.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Schema.pm
Type: application/x-perl
Size: 542 bytes
Desc: not available
Url : http://rectangular.com/pipermail/kinosearch/attachments/20081209/7e354fae/attachment-0007.bin