From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: 73310@debbugs.gnu.org, hi@vinurs.me
Subject: bug#73310: tree-sitter makes cpu 100%
Date: Fri, 20 Dec 2024 14:15:49 +0200 [thread overview]
Message-ID: <86ldwaa6tm.fsf@gnu.org> (raw)
In-Reply-To: <71C7B1A0-AFD4-4162-A670-9749B1C0CD41@gmail.com> (message from Yuan Fu on Fri, 20 Dec 2024 01:14:04 -0800)
> From: Yuan Fu <casouri@gmail.com>
> Date: Fri, 20 Dec 2024 01:14:04 -0800
> Cc: vinurs <hi@vinurs.me>,
> 73310@debbugs.gnu.org
>
> > On Dec 20, 2024, at 12:37 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > Can we have a GDB backtrace when Emacs freezes like that? If the
> > freeze is inside tree-sitter, maybe build that with debug symbols, so
> > that GDB shows information inside the library, and we could then try
> > to figure out what causes this.
>
> It’s almost certainly tree-sitter. And it’s unlikely for us to find the cause of the hang without considerable knowledge of tree-sitter internals.
Maybe. But we have the sources of tree-sitter, so nothing prevents us
from trying -- provided that we have the backtrace from the freeze.
> Anyway, I’ll start with reproducing it reliably.
Thanks, that will help.
prev parent reply other threads:[~2024-12-20 12:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 1:27 bug#73310: tree-sitter makes cpu 100% vinurs
2024-09-17 12:29 ` Eli Zaretskii
2024-09-19 12:53 ` vinurs
2024-09-20 6:50 ` Yuan Fu
2024-11-10 11:22 ` vinurs
2024-11-10 11:28 ` Eli Zaretskii
2024-11-10 11:35 ` vinurs
2024-11-25 1:48 ` Yuan Fu
2024-11-25 11:21 ` vinurs
2024-12-07 12:22 ` Eli Zaretskii
2024-12-11 7:04 ` Yuan Fu
2024-12-11 7:44 ` vinurs
2024-12-11 8:10 ` vinurs
2024-12-12 4:52 ` Yuan Fu
2024-12-18 15:22 ` vinurs
2024-12-19 18:33 ` Yuan Fu
2024-12-19 21:34 ` vinurs
2024-12-20 8:25 ` Yuan Fu
2024-12-20 8:37 ` Eli Zaretskii
2024-12-20 9:14 ` Yuan Fu
2024-12-20 12:15 ` Eli Zaretskii [this message]
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=86ldwaa6tm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73310@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=hi@vinurs.me \
/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).