unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Michael Albinus" <michael.albinus@gmx.de>,
	"Alexander Prähauser" <ahprae@protonmail.com>
Cc: 69835@debbugs.gnu.org, Noah Friedman <noah@splode.com>
Subject: bug#69835: Fwd: Eldoc drastically increases CPU usage after update
Date: Sun, 17 Mar 2024 08:07:09 +0200	[thread overview]
Message-ID: <86bk7d5r3m.fsf@gnu.org> (raw)
In-Reply-To: <6baad279-400c-4da1-9d6e-20bba211dc64@splode.com> (message from Noah Friedman on Sat, 16 Mar 2024 17:08:05 -0700 (PDT))

> Date: Sat, 16 Mar 2024 17:08:05 -0700 (PDT)
> From: Noah Friedman <noah@splode.com>
> 
> Please mark original sender as the reporter. Thanks.

I don't know what that means in practice, sorry.  Michael, can you
help?

> From: Alexander Prähauser <ahprae@protonmail.com>
> To: Noah Friedman <friedman@splode.com>
> Date: Feb 13, 2024 08:57:32
> Subject: Eldoc drastically increases CPU usage after update
> 
> After I recently (within a week) updated my system and Emacs, I noticed that Emacs was a
> lot slower and needed more power than previously. I deactivated all
> minor modes and re-activated them one after the other, and found that
> editing speed decreased drastically when I re-activated Eldoc mode.
> Emacs version returns
> 
> GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, cairo version 1.18.0) of 2024-02-08
> 
> My system is Arch with the newest updates. Please let me know if I can do anything to help with debugging.

Please tell what was the previous HEAD against which you measure the
performance.  The latest change in eldoc.el was on Feb 23 and was
related to obarray changes; I find it hard to believe that change
could have had such an effect.  The change before that was on Jan 20.
Both are outside of the "within a week" period you seem to be
referring to.

A recipe to reproduce the problem starting from "emacs -Q" would be
nice.





  reply	other threads:[~2024-03-17  6:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-17  0:08 bug#69835: Fwd: Eldoc drastically increases CPU usage after update Noah Friedman
2024-03-17  6:07 ` Eli Zaretskii [this message]
2024-03-17  8:10   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=86bk7d5r3m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69835@debbugs.gnu.org \
    --cc=ahprae@protonmail.com \
    --cc=michael.albinus@gmx.de \
    --cc=noah@splode.com \
    /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).