From: Aaron Jensen <aaronjensen@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46384@debbugs.gnu.org
Subject: bug#46384: 28.0.50; 100% cpu in line_number_display_width
Date: Thu, 16 Jun 2022 18:40:46 -0400 [thread overview]
Message-ID: <CAHyO48yd5WJaDPJDi+6UB6oqgujc9+-YM=rEwALig2m7nNVBrQ@mail.gmail.com> (raw)
In-Reply-To: <874k0kd96n.fsf@gnus.org>
On Thu, Jun 16, 2022 at 9:33 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> 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?
I don't think I've seen it recently, feel free to close. Thank you.
next prev parent reply other threads:[~2022-06-16 22:40 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
2022-06-16 22:40 ` Aaron Jensen [this message]
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
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='CAHyO48yd5WJaDPJDi+6UB6oqgujc9+-YM=rEwALig2m7nNVBrQ@mail.gmail.com' \
--to=aaronjensen@gmail.com \
--cc=46384@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).