[KinoSearch] Possible bug in Kinosearch::Invindexer

[Nils Grunwald]

Thanks a lot for the bugfix about the memory leak, it was indeed 
insidious, I spent half a day using valgrind and not understanding why i 
could not find any leak. That's why I wondered if there was some 
undocumented step to release the objects. The leaks are indeed gone from 
rev 3972. However, while testing the new rev, I think I found a new bug 
in Invindexer, less insidious I hope. It can be reproduced with almost 
the same script as last time: if indexing a large number of documents 
without calling finish, Invindexer crashes while adding a document or 
while finishing with this error message:

Can't write to a closed OutStream at 
../c_src/KinoSearch/Store/OutStream.c:80 do_flush

The invindexer always crashes at the same iteration of the loop, but the 
exact iteration depends on the docs size and the machine on which it is 
running. I have confirmed the same test case runs fine under rev 3892. I 
join the updated test case script. Please tell me if there is anything 
else I can do, and again thanks for all you work.

Cheers,

Nils Grunwald
-------------- next part --------------
A non-text attachment was scrubbed...
Name: minimal.pl
Type: application/x-perl
Size: 646 bytes
Desc: not available
Url : http://rectangular.com/pipermail/kinosearch/attachments/20081222/f0dc6599/attachment-0004.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/20081222/f0dc6599/attachment-0005.bin