From: Ken Goldman <kgoldman@us.ibm.com>
To: help-gnu-emacs@gnu.org
Subject: Re: How to debug high CPU usage -> hang
Date: Wed, 11 Jan 2023 15:24:53 -0500 [thread overview]
Message-ID: <tpn5ul$ms7$1@ciao.gmane.io> (raw)
In-Reply-To: <831qo2o1p2.fsf@gnu.org>
On 1/10/2023 10:21 AM, Eli Zaretskii wrote:
>> From: Ken Goldman <kgoldman@us.ibm.com>
>> Date: Tue, 10 Jan 2023 09:58:58 -0500
>>
>> I'm editing in ReST mode, Windows 11, emacs 28.1.
>>
>> Occasionally, I want to jump (search, etc.) and the CPU usage jumps and
>> emacs hangs. I suspect a font-lock issue.
>>
>> I fixed one by bisecting the text, then changing a table type. Now I
>> have another.
>>
>> Is there a general way to debug?
>
> I can suggest profiling and/or attaching a debugger.
>
Attaching a debugger to the lisp major mode, or building emacs from
source?
next prev parent reply other threads:[~2023-01-11 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 14:58 How to debug high CPU usage -> hang Ken Goldman
2023-01-10 15:21 ` Eli Zaretskii
2023-01-11 20:24 ` Ken Goldman [this message]
2023-01-12 7:36 ` Eli Zaretskii
2023-01-12 10:36 ` Manuel Giraud
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='tpn5ul$ms7$1@ciao.gmane.io' \
--to=kgoldman@us.ibm.com \
--cc=help-gnu-emacs@gnu.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.
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).