From: Carl Worth <cworth@cworth.org>
To: Dominik Epple <dominik.epple@googlemail.com>, notmuch@notmuchmail.org
Subject: Re: notmuch new: Memory problem
Date: Fri, 20 Nov 2009 21:56:32 +0100 [thread overview]
Message-ID: <87skc8oqyn.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <123554aa0911200056h73def158pb0db64a2a78ed687@mail.gmail.com>
On Fri, 20 Nov 2009 09:56:50 +0100, Dominik Epple <dominik.epple@googlemail.com> wrote:
> Is there a problem with the number of my mails? I currently have over
> 40.000 Mails... they live currently in mbox files, I created a Maildir
> with mb2md-3.20.pl.
I'm suspecting that you have some big files in there, (such as indexes
from some other mail program). We had code in notmuch to detect and
ignore these, but a recent bug had broken that.
I just fixed this code as of the below commit. So please update and try
again and let us know if things work any better.
Thanks for your patience!
-Carl
commit 3ae12b1e286d1c0041a2e3957cb01daa2981dad9
Author: Carl Worth <cworth@cworth.org>
Date: Fri Nov 20 21:46:37 2009 +0100
add_message: Re-fix handling of non-mail files.
More fallout from _get_header now returning "" for missing headers.
The bug here is that we would no longer detect that a file is not an
email message and give up on it like we should.
And this time, I actually audited all callers to
notmuch_message_get_header, so hopefully we're done fixing this
bug over and over.
next prev parent reply other threads:[~2009-11-20 20:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 8:56 notmuch new: Memory problem Dominik Epple
2009-11-20 16:01 ` Carl Worth
2009-11-23 15:30 ` Dominik Epple
2009-11-20 20:56 ` Carl Worth [this message]
2009-11-23 16:26 ` Dominik Epple
2009-11-25 9:39 ` Dominik Epple
2009-11-26 18:46 ` Carl Worth
2009-11-26 19:16 ` Carl Worth
2010-02-05 18:59 ` notmuch new: Memory problem (with uuencoded content) Carl Worth
2010-02-06 10:40 ` Michal Sojka
2010-02-06 21:45 ` Carl Worth
2010-02-08 14:19 ` Michal Sojka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87skc8oqyn.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=dominik.epple@googlemail.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).