GNU bug report logs - #73046
29.4; Emacs 100% CPU usage for several seconds when opening dired buffer over TRAMP

Previous Next

Package: emacs;

Reported by: "Suhail Singh" <suhailsingh247 <at> gmail.com>

Date: Thu, 5 Sep 2024 14:56:01 UTC

Severity: normal

Found in version 29.4

Fixed in version 31.1

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log

Message #167 received at 73046 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Suhail Singh <suhailsingh247 <at> gmail.com>
Cc: michael.albinus <at> gmx.de, 73046 <at> debbugs.gnu.org
Subject: Re: bug#73046: 29.4; Emacs 100% CPU usage for several seconds when
 opening dired buffer over TRAMP
Date: Sun, 15 Sep 2024 08:55:32 +0300

> From: Suhail Singh <suhailsingh247 <at> gmail.com>
> Cc: Suhail Singh <suhailsingh247 <at> gmail.com>,  michael.albinus <at> gmx.de,
>   73046 <at> debbugs.gnu.org
> Date: Sat, 14 Sep 2024 18:36:04 -0400
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > If 3 surprised you, then the reason is simple: sit-for returns
> > immediately if any input is available, so typing effectively disables
> > the wait.
> 
> Interesting.  I didn't expect it to do so persistently (i.e., for
> subsequent iterations of the while loop in question).

Since the command still runs, your type-ahead is not consumed, and
each sit-for exits immediately.
This bug report was last modified 240 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.