[KinoSearch] Memory leak in KinoSearch::Index::PostingsWriter::add_batch

[Dan Sully]

* Marvin Humphrey shaped the electrons to say...

>It's either a true leak, or something else is wrong -- Dan's numbers  
>are definitely bigger than they should be.   I think around 45-50  
>megs ought to be worst case for an InvIndexer in 0.20_04 (and we can  
>bring that down in future releases).
>
>Tracking leaks in a Perl app with valgrind is a little tricky.

I'm trying to run under valgrind right now.. current size is 186M.

>Thanks for the report, Dan.  I'll attend to this when I can take a  
>break from fighting fires at $contract_job.

No problem.

-D
--
<dsully> please describe web 2.0 to me in 2 sentences or less.
<jwb> you make all the content. they keep all the revenue.