Re: read after free in notmuch new

Subject: Re: read after free in notmuch new

Date: Sun, 19 Feb 2017 11:29:53 -0400



From: David Bremner

David Bremner <> writes:

> I haven't had a chance to really track this down, but it seems there is
> a memory error in notmuch new (or a maybe false positive from valgrind).
> Attached is the log from running "make memory-test OPTIONS=--medium" on
> current git master (0e037c34).
> It looks like we talloc the message_id string with the message object as
> parent, but it somehow outlives the message object.

Sorry, that had a few commits beyond master.

master (08343d3d) gives essentially the same log.

1.log (application/octet-stream)