From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Justin Van Winkle Newsgroups: gmane.emacs.bugs 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 14:55:22 -0400 Message-ID: References: <878t2gbisr.fsf@gmx.de> <83pnvskl8b.fsf@gnu.org> <83lg6fjq6f.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000ff6425057976baa3" X-Trace: blaine.gmane.org 1540925654 29454 195.159.176.226 (30 Oct 2018 18:54:14 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 30 Oct 2018 18:54:14 +0000 (UTC) Cc: michael.albinus@gmx.de, 33194@debbugs.gnu.org To: eliz@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Oct 30 19:54:09 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gHZ9V-0007Xr-LB for geb-bug-gnu-emacs@m.gmane.org; Tue, 30 Oct 2018 19:54:09 +0100 Original-Received: from localhost ([::1]:55023 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gHZBb-0000ZZ-NC for geb-bug-gnu-emacs@m.gmane.org; Tue, 30 Oct 2018 14:56:19 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56014) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gHZBP-0000Vy-DR for bug-gnu-emacs@gnu.org; Tue, 30 Oct 2018 14:56:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gHZBK-0007Y9-Ag for bug-gnu-emacs@gnu.org; Tue, 30 Oct 2018 14:56:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:51666) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gHZBK-0007XI-6y for bug-gnu-emacs@gnu.org; Tue, 30 Oct 2018 14:56:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gHZBK-000571-63 for bug-gnu-emacs@gnu.org; Tue, 30 Oct 2018 14:56:02 -0400 X-Loop: help-debbugs@gnu.org In-Reply-To: Resent-From: Justin Van Winkle Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 30 Oct 2018 18:56:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 33194 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 33194-submit@debbugs.gnu.org id=B33194.154092574419621 (code B ref 33194); Tue, 30 Oct 2018 18:56:02 +0000 Original-Received: (at 33194) by debbugs.gnu.org; 30 Oct 2018 18:55:44 +0000 Original-Received: from localhost ([127.0.0.1]:55923 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gHZB1-00056M-Nc for submit@debbugs.gnu.org; Tue, 30 Oct 2018 14:55:44 -0400 Original-Received: from mail-lj1-f171.google.com ([209.85.208.171]:45124) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gHZAz-000566-DO for 33194@debbugs.gnu.org; Tue, 30 Oct 2018 14:55:41 -0400 Original-Received: by mail-lj1-f171.google.com with SMTP id j4-v6so12427001ljc.12 for <33194@debbugs.gnu.org>; Tue, 30 Oct 2018 11:55:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:from:date:message-id:subject:to:cc; bh=pNg7at+ZlpWuFI2lEuMj42LsjjaOrmDQWuG5ovb3fpc=; b=GbdNBvQF/MovS3jp3WZDtF4m60U5wGPsgdzuVt/mJnSCWfnRwIoE0Z0a45+B127LFv Mx2WX5yrAjCHE2dZd1Ss1y3kGVnWu4uGGXFsve00YcZem1HtHLKmLKonOwW0bcrc9xVu N1CSVyhnHPS0z9RHbTJh2xlISSnaGsU7BGljmabvA+3CgJxJ6js5jwT8w3Xr+Zdr0GKA u6RlVitfaDhsgOcSnZsgCybzRII2JwGSUvSS35U4cn6QYLQ6RQC5SWabZ8TLJlMfeA2g xNziV6rO7gDzQEmZ1ZluAUa29SnJX/C3qK7ZVlG4MjbQgRLg4sVCxPnJx85oRpnNpMTn 4G0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:from:date:message-id :subject:to:cc; bh=pNg7at+ZlpWuFI2lEuMj42LsjjaOrmDQWuG5ovb3fpc=; b=LLdmJGt7NQUBvBdrJAWLX5R/ZMAms0t+4Ng7BgofvELQ88putQ45T4yVh0p8SyyjjU oYjuf4MoXjh2rRKjVnS3Epi7gp1JMrxFZuHcueOvaPk1KHonpnltJ3IiOAzN4XERhBWq D57d2qbHrXT9g5+icBUW7ZONGnksKgv/87e9quxKJUgMz39lSaOLw+ZJn0/nJFaMHfEF rXBgiTFQrACbybC6m/ma1rOVS0isJRE1xzyu7NKxWpFI8NZR6zmzNphSuGYikJIN+nip agBJSn6n23vzLX5Hw/7uwIw7e07dqlB63B7BJOztpoUKJn+DZoJyK1zcMZF8xbBlJkAE NXDA== X-Gm-Message-State: AGRZ1gJB/6cipX0wyh5w2lOcONEk+0u0d38Xxo3ZPGZyEr++gCrGguTg TOiSv0AeF0hrS/dEcw6jIaLw7p8BU4jwX20nNkNObqhW X-Google-Smtp-Source: AJdET5ejIvz2YYIhN58pOBmfN1FwgekNw6NbbKiaJiPJ2Era8Ree23Te5gyUYDCe0QoeB5Gd6Ibh1kwf0HsU6dG3aIg= X-Received: by 2002:a2e:824c:: with SMTP id j12-v6mr51614ljh.168.1540925733953; Tue, 30 Oct 2018 11:55:33 -0700 (PDT) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:151843 Archived-At: --000000000000ff6425057976baa3 Content-Type: text/plain; charset="UTF-8" I mean it is certainly a bug to use 100% of a cpu just because a file that is in the same directory to a file you are editing is being written to, but it may not be unintentional behavior. On Tue, Oct 30, 2018 at 2:54 PM Justin Van Winkle < justin.vanwinkle@gmail.com> wrote: > Ok, in that case I wonder if this is actually a bug. > > On Tue, Oct 30, 2018 at 1:33 PM Eli Zaretskii wrote: > >> > From: Justin Van Winkle >> > Date: Tue, 30 Oct 2018 12:18:34 -0400 >> > Cc: michael.albinus@gmx.de, 33194@debbugs.gnu.org >> > >> > To clarify, I was not writing to a file that was open in emacs. In >> fact, emacs would use 100% cpu even with no >> > files opened, so long as global-auto-revert-mode was activated. >> >> That was clear. Like I said: auto-revert mode makes Emacs watch >> changes to _any_ file in that file's directory. >> > --000000000000ff6425057976baa3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I mean it is certainly a bug to use 100% of a cpu just bec= ause a file that is in the same directory to a file you are editing is bein= g written to, but it may not be unintentional behavior.

On Tue, Oct 30, 2018 at 2:54 PM Justin Va= n Winkle <justin.vanwinkle= @gmail.com> wrote:
Ok, in that case I wonder if this is actually a bug.=C2=A0=C2=A0
On Tue, Oct 30, 2018 at= 1:33 PM Eli Zaretskii <eliz@gnu.org= > wrote:
> From: Justin Van W= inkle <j= ustin.vanwinkle@gmail.com>
> Date: Tue, 30 Oct 2018 12:18:34 -0400
> Cc: michae= l.albinus@gmx.de, 33194@debbugs.gnu.org
>
> To clarify, I was not writing to a file that was open in emacs.=C2=A0 = In fact, emacs would use 100% cpu even with no
> files opened, so long as global-auto-revert-mode was activated.

That was clear.=C2=A0 Like I said: auto-revert mode makes Emacs watch
changes to _any_ file in that file's directory.
--000000000000ff6425057976baa3--