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

[Nathan Kurz]

On 7/30/07, Dan Sully <daniel at electricrain.com> wrote:
> Unfortunately I don't understand where kino_PostWriter_add_batch() is defined.

Presumably Marvin is busy with something, so I'll try an interim
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.

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.

Good luck!

Nathan Kurz
nate at verse.com