From: Gregor Zattler <telegraph@gmx.net>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: OOM killer hits emacs on thread with 439 messages
Date: Sat, 01 Apr 2017 21:12:45 +0200 [thread overview]
Message-ID: <87wpb49c2a.fsf@len.workgroup> (raw)
In-Reply-To: <87k274nep4.fsf@tesseract.cs.unb.ca>
Hi David,
actually, this was a false alarm: I didn't re-test before posting:
Actually it works with emacs -Q and with my full configuration.
Sorry for the noise, Gregor
* David Bremner <david@tethera.net> [2017-04-01; 15:52]:
> Gregor Zattler <telegraph@gmx.net> writes:
>
>> Hi, this thread from emacs-devel:
>>
>> Yest. 10:40 [4/309] Eli Zaretskii, Ken Raeburn, npostavs@users.sourceforge.net, Paul Eggert, Stefan Monnier, Andreas Schwab, Richard Stallman, Lars Ingebrigtsen, Daniel Colascione, Philipp Stephani, Lars Brinkhoff, Perry E. Metzger, Noam Postavsky, Fabrice Popineau, Jérémie Courrèges-Anglas, Simon Leinen, Alp Aker, Ken Brown, Phil Sainty, Yuri Khan, Clément Pit--Claudel, Robert Pluim, Phillip Lord, Alan Mackenzie Skipping unexec via a big .elc file (attachment inbox signed unread)
>>
>> brought notmuch-emacs to a grinding halt on a system which
>> otherwise was used far below memory capapilities (8G RAM, 4.5GB
>> swap, AMD64, emacs compiled from source with 64 bit), later the
>> OMM killer got it.
>>
>
> No, that's definitely a bug. Hard to say if it's a bug in emacs or in
> notmuch-emacs. Can you make an mbox out of the thread (e.g. with notmuch
> show --format=mbox thread:whatever) and either put it somewhere or mail
> it to me (if it's below 2M). I'd do it myself but it lokos like I'd need
> to download at least 4 months of archives.
>
> It's always good to specify what version of emacs and what version of
> notmuch you encounter problems with.
>
> d
prev parent reply other threads:[~2017-04-01 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 17:11 OOM killer hits emacs on thread with 439 messages Gregor Zattler
2017-04-01 18:52 ` David Bremner
2017-04-01 19:12 ` Gregor Zattler [this message]
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=87wpb49c2a.fsf@len.workgroup \
--to=telegraph@gmx.net \
--cc=david@tethera.net \
--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).