From: Lars Ingebrigtsen <larsi@gnus.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 46384@debbugs.gnu.org
Subject: bug#46384: 28.0.50; 100% cpu in line_number_display_width
Date: Thu, 16 Jun 2022 15:33:52 +0200 [thread overview]
Message-ID: <874k0kd96n.fsf@gnus.org> (raw)
In-Reply-To: <m1ft26k1x3.fsf@gmail.com> (Aaron Jensen's message of "Mon, 08 Feb 2021 09:35:36 -0600")
Aaron Jensen <aaronjensen@gmail.com> writes:
> When I woke my computer from sleep this morning, Emacs was at 100% cpu
> and stuck there.
>
> Unfortunately, I cannot reproduce this reliably and I wasn't running a
> debug build when it happened so I was only able to get the backtrace. I
> tried very hard to get information from the debugger but with all the
> macros inlined it was a bit beyond me to expand the macros manually.
> Note that my configure flags below are from when I recompiled with -Og,
> rather than the build I actually saw the 100% cpu run on.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
Do you still see this issue in recent Emacs versions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-16 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 15:35 bug#46384: 28.0.50; 100% cpu in line_number_display_width Aaron Jensen
2021-02-09 6:11 ` Richard Stallman
2021-02-09 7:18 ` Eli Zaretskii
2021-02-10 5:28 ` Richard Stallman
2021-02-10 11:16 ` Eli Zaretskii
2021-02-11 13:37 ` Richard Stallman
2021-02-10 14:12 ` Robert Pluim
2021-02-10 16:06 ` Aaron Jensen
2021-02-10 16:18 ` Aaron Jensen
2021-02-10 17:54 ` Robert Pluim
2021-02-11 13:37 ` Richard Stallman
2022-06-16 13:33 ` Lars Ingebrigtsen [this message]
2022-06-16 22:40 ` Aaron Jensen
2022-06-17 12:02 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874k0kd96n.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=46384@debbugs.gnu.org \
--cc=aaronjensen@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.