From: Eli Zaretskii <eliz@gnu.org>
To: Justin Van Winkle <justin.vanwinkle@gmail.com>
Cc: michael.albinus@gmx.de, 33194@debbugs.gnu.org
Subject: bug#33194: 26.1; Auto-revert mode causes emacs to use 100% cpu whenever a file is being written to in the home directory
Date: Tue, 30 Oct 2018 08:21:56 +0200 [thread overview]
Message-ID: <83pnvskl8b.fsf@gnu.org> (raw)
In-Reply-To: <CA+gsFkJgpWNZ=2iOaMtdpbHH8UT3tAiJthv+1Fcy9obNWO58Ww@mail.gmail.com> (message from Justin Van Winkle on Mon, 29 Oct 2018 17:13:22 -0400)
> From: Justin Van Winkle <justin.vanwinkle@gmail.com>
> Date: Mon, 29 Oct 2018 17:13:22 -0400
> Cc: 33194@debbugs.gnu.org
>
> It was outside of emacs. SCP would trigger the cpu usage in emacs, rsync would not (oddly). Both "cat
> /dev/zero > somefile" and "dd if=/dev/zero of=somefile" would trigger it if somefile was in my $HOME
> directory, but none of these would trigger it if I did it in, for example, $HOME/Downloads/
Isn't this expected? Auto-revert watches the directory of the file,
so if a lot of changes happen in that directory, Emacs will get a lot
of file-change notifications, and will need to process them.
If you don't like this, customize auto-revert-use-notify to not use
notifications. Or maybe there's some system-wide customization of
inotify that determine the max frequency of inotify notifications when
the changes are to the same file. (I don't know enough about inotify
to say anything more specific, sorry.)
next prev parent reply other threads:[~2018-10-30 6:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 16:01 bug#33194: 26.1; Auto-revert mode causes emacs to use 100% cpu whenever a file is being written to in the home directory Justin Van Winkle
2018-10-29 20:27 ` Michael Albinus
2018-10-29 21:13 ` Justin Van Winkle
2018-10-29 21:14 ` Justin Van Winkle
2018-10-30 6:21 ` Eli Zaretskii [this message]
2018-10-30 8:39 ` Michael Albinus
2018-10-30 10:41 ` Eli Zaretskii
2018-10-30 10:44 ` Michael Albinus
2018-10-30 12:28 ` Eli Zaretskii
2018-10-30 13:12 ` Michael Albinus
2018-10-30 16:18 ` Justin Van Winkle
2018-10-30 16:58 ` Michael Albinus
2018-10-30 17:02 ` Justin Van Winkle
2018-10-30 17:08 ` Michael Albinus
2018-10-30 17:09 ` Justin Van Winkle
2018-10-30 17:32 ` Eli Zaretskii
2018-10-30 18:54 ` Justin Van Winkle
2018-10-30 18:55 ` Justin Van Winkle
2018-11-03 10:57 ` Michael Albinus
2018-11-04 11:58 ` Michael Albinus
2018-11-05 16:28 ` Justin Van Winkle
2018-11-05 21:18 ` Michael Albinus
2019-01-04 12:56 ` Michael Albinus
2019-03-28 12:36 ` Michael Albinus
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pnvskl8b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33194@debbugs.gnu.org \
--cc=justin.vanwinkle@gmail.com \
--cc=michael.albinus@gmx.de \
/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://git.savannah.gnu.org/cgit/emacs.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).