GNU bug report logs - #37000
27.0.50; gc and laggy Emacs

Previous Next

Package: emacs;

Reported by: Alex Branham <alex.branham <at> gmail.com>

Date: Sat, 10 Aug 2019 16:28:02 UTC

Severity: normal

Found in version 27.0.50

Done: Alex Branham <alex.branham <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Stefan Kangas <stefan <at> marxist.se>
To: Alex Branham <alex.branham <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 37000 <at> debbugs.gnu.org
Subject: bug#37000: 27.0.50; gc and laggy Emacs
Date: Tue, 25 Aug 2020 17:15:33 -0700
Alex Branham <alex.branham <at> gmail.com> writes:

> On Sat 10 Aug 2019 at 19:50, Eli Zaretskii <eliz <at> gnu.org> wrote:
>
>>> From: Alex Branham <alex.branham <at> gmail.com>
>>> Date: Sat, 10 Aug 2019 11:27:29 -0500
>>>
>>> Recently I've noticed Emacs sometimes getting _very_ laggy, as in
>>> taking up to a half-second to display the a single character that
>>> I type. M-x profiler-start suggests that garbage-collection is
>>> taking up too much time (see below my signature for example
>>> output). gc-cons-percentage and gc-cons-threshold are at their
>>> default values. I can't figure out how to reproduce this reliably,
>>> but running M-x relint-directory on the Emacs source tree seems to
>>> do a decent job triggering it. My Emacs is built from commit
>>> 4ce9c6d0b58bd77bc811d6c1c5caf955a5a0be2f (~ 4 days ago) of the
>>> master branch. How can I go about tracking this down?
>>
>> Trying to bisect to find the offending commit would be one way.
>
> Thanks. I noticed there's some activity around gc on master currently.
> I'll wait for that to pass before trying this.
>
> I'll note though that I don't see this issue on 26.2.

(That was one year ago.)

Any updates here?




This bug report was last modified 4 years and 327 days ago.

Previous Next


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