read after free in notmuch new

David Bremner david at
Sun Feb 19 06:15:07 PST 2017

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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.log
Type: application/octet-stream
Size: 32040 bytes
Desc: not available
URL: <>

More information about the notmuch mailing list