'notmuch new' leaking memory and getting slower over time?

[David Bremner]

Petter Reinholdtsen <pere at hungry.com> writes:
> Running 'notmuch restore' to get my tags back took 106 minutes, and I
> was very surprised that the restore could not load all the tags stored
> by 'notmuch dump'.  The restore complained about this line:
>
>   NO*TELEMAX**NORWAYII  M0018001012307699038 (unread usit year-2002)
>
> The message in question is a bounce from some X400 mail system, and its
> message id look like this:
>
>   Message-Id: <NO*TELEMAX**NORWAYII    M0018001012307699038>
>
> I would like 'notmuch new' to use less memory and be better at
> estimating the time left, and would also like 'notmuch restore' to
> always be able to load the output from 'notmuch dump'.

As of git commit 0.14-162-g5c7990f, notmuch supports a new dump restore
format 'batch-tag' that can handle these message-id's.  See the man
pages for more details.

I'm marking this bug as fixed; feel free to let us know of any problems
with the new batch-tag format.

d