From: Eli Zaretskii <eliz@gnu.org>
To: Peter Ludemann <peter.ludemann@gmail.com>
Cc: 38644@debbugs.gnu.org
Subject: bug#38644: 26.3; emacs uses 100% CPU with auto-revert-mode
Date: Tue, 17 Dec 2019 18:17:04 +0200 [thread overview]
Message-ID: <83fthj3p1b.fsf@gnu.org> (raw)
In-Reply-To: <CAHjfyZ2W03Ju7CCu4gAczT3noxg4qzsKv8QN7H_j0v5uJBg1NA@mail.gmail.com> (message from Peter Ludemann on Mon, 16 Dec 2019 17:23:30 -0800)
> From: Peter Ludemann <peter.ludemann@gmail.com>
> Date: Mon, 16 Dec 2019 17:23:30 -0800
>
> My hypothesis is that emacs is monitoring some files that it shouldn't
Emacs actually monitors the directory of every file whose buffer has
auto-revert-mode turned on, if you use file notifications for
auto-reverting (which is the default).
> When I run a CPU-bound job that also does quite a bit of I/O, emacs
> becomes very unresponsive -- running "top", I see CPU usage for emacs go
> into the 50-100% range.
Does "a bit of I/O" includes creating, deleting, or modifying files in
a directory where you have a file whose buffer has auto-revert-mode?
> As far as I know, I don't have any of the output files or directories
> open (I have global-auto-revert-mode set) -- all the outputs go into one
> directory and when I search the Buffer List, I don't see that
> directory.
Turn off auto-revert-use-notify and try again, would be my advice.
next prev parent reply other threads:[~2019-12-17 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 1:23 bug#38644: 26.3; emacs uses 100% CPU with auto-revert-mode Peter Ludemann
2019-12-17 13:59 ` Michael Albinus
2019-12-17 16:17 ` Eli Zaretskii [this message]
2019-12-17 18:27 ` Peter Ludemann
2019-12-17 19:30 ` Michael Albinus
2019-12-28 21:12 ` Peter Ludemann
2019-12-29 15:23 ` Michael Albinus
2020-01-04 18:50 ` Peter Ludemann
2020-01-05 9:28 ` Michael Albinus
2020-01-05 13:04 ` Mattias Engdegård
2020-01-05 19:31 ` Peter Ludemann
2020-01-05 19:57 ` Mattias Engdegård
2020-01-07 0:01 ` Peter Ludemann
2020-01-07 0:34 ` Peter Ludemann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fthj3p1b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38644@debbugs.gnu.org \
--cc=peter.ludemann@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.