Python3: memory leak

[Sean Robinson]

I may have found a memory leak in Xapian 1.3+ with Python3. This exhibits itself when multiple indexing runs are done back-to-back without exiting the indexing program. I have tested this under Valgrind and it reports lost memory.

[Sean Robinson]

tar.gz of files used to test under Valgrind

[Olly Betts]

Thanks for the report.

There's a leak in the code to convert a string from Python to C++, which I've fixed in [c53ba8acd4862057fbbe478025962ef089bd7a1f] on master and backported to RELEASE/1.4 in [ ca8b8416bb6d4609b5e801fcd7347209893333f8] (so this should be fixed in 1.4.1).

I now get:

==19170==    definitely lost: 0 bytes in 0 blocks
==19170==    indirectly lost: 0 bytes in 0 blocks
==19170==      possibly lost: 4,576 bytes in 7 blocks
==19170==    still reachable: 987,276 bytes in 900 blocks
==19170==         suppressed: 87,615 bytes in 37 blocks

The "possibly lost" probably aren't actual leaks - that means there's a pointer into an allocated block, but not to the start of it - snowball's code does that for example, and I think some of the C++ STL does too.