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

[Dan Sully]

* Nathan Kurz shaped the electrons to say...

>answer.  I haven't looked much at the Index creation side of things,
>but that would be defined in c_src/KinoSearch/Index/PostingsWriter.c
>as PostWriter_add_batch().
>The "kino_" part is caused by the BoilerPlater layer, which defines a
>class hierarchy for the C level objects, and probably can be ignored
>here.

Aha! I didn't look above the perl/ tree.

>Glancing at the code, it sees like you can specify a 'mem_thresh'
>parameter when creating the PostWriter object.  This gets passed
>through the the underlying MemPool object
>(c_src/KinoSearch/Util/MemoryPool.c).  If it's a true leak (as opposed
>to just  large buffer) it might be easiest to track down with
>valgrind.

Yeah, tried passing in 2k for the mem_thresh, but that didn't work.

-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.