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.
>>
>