https://bugs.kde.org/show_bug.cgi?id=363741

Olly Betts <ojwbetts+...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ojwbetts+...@gmail.com

--- Comment #32 from Olly Betts <ojwbetts+...@gmail.com> ---
> There was an undocumented behaviour change in Xapian 1.4

Otherwise known as a "bug"!  In this case the behaviour change is the bug, but
even if it was deliberate not documenting it would still be a bug.

It would be helpful to forwards reports of such things to the Xapian developers
so we can actually address them.  In this case I happened to stumble across
your report via the Debian BTS when checking for any fallout from the
transition to xapian 1.4 that Debian has just completed - clearly that's not a
reliable or timely way to find out about an issue.  If this had been forwarded
when first reported, we could have fixed it before 1.4.0.

The fix applied in 1e70d63a9439f48b5f1a70accac531a10f4e4239 leaks the
AgePostingSource object - with 1.4.0 your best option is to hand over ownership
like so:

    return Xapian::Query(Xapian::Query::OP_AND_MAYBE, query, Xapian::Query((new
AgePostingSource(0))->release()));

Hopefully there's still a way we can fix this without breaking compatibility
with 1.4.0.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to