From: Justin Van Winkle <justin.vanwinkle@gmail.com>
To: michael.albinus@gmx.de
Cc: 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: Mon, 29 Oct 2018 17:14:33 -0400 [thread overview]
Message-ID: <CA+gsFkKB1K8fDyr8r42CWPbU=pJWPMR9B98Z6RaXtMv4LWr53A@mail.gmail.com> (raw)
In-Reply-To: <CA+gsFkJgpWNZ=2iOaMtdpbHH8UT3tAiJthv+1Fcy9obNWO58Ww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Disabling global-revert-buffer-mode also led to emacs not using cpu.
On Mon, Oct 29, 2018 at 5:13 PM Justin Van Winkle <
justin.vanwinkle@gmail.com> wrote:
> Hi Michael,
>
> 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/
>
> I am pretty sure I can reproduce this at will if you need.
>
> - Justin
>
> On Mon, Oct 29, 2018 at 4:27 PM Michael Albinus <michael.albinus@gmx.de>
> wrote:
>
>> Justin Van Winkle <justin.vanwinkle@gmail.com> writes:
>>
>> Hi Justin,
>>
>> > I enable global-auto-revert-mode. I noticed that when I was scp'ing a
>> > large file to my home directory, every emacs process on my machine was
>> > trying to use 100% cpu. When I stopped the file transfer, emacs would
>> > go back to idle cpu usage. I ran the emacs profiler and narrowed it
>> > down to revert-buffer. Auto revert was apparently listening for
>> > changes in my home directory, even for things like file creation or
>> > file modified for files emacs did not have open.
>>
>> How did you "scp'ing a large file"? Inside Emacs, using Tramp, or
>> outside Emacs?
>>
>> Best regards, Michael.
>>
>
[-- Attachment #2: Type: text/html, Size: 2071 bytes --]
next prev parent reply other threads:[~2018-10-29 21:14 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 [this message]
2018-10-30 6:21 ` Eli Zaretskii
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='CA+gsFkKB1K8fDyr8r42CWPbU=pJWPMR9B98Z6RaXtMv4LWr53A@mail.gmail.com' \
--to=justin.vanwinkle@gmail.com \
--cc=33194@debbugs.gnu.org \
--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).