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 10:37:21 +0200 [thread overview]
Message-ID: <86msgqagxq.fsf@gnu.org> (raw)
In-Reply-To: <42BD4BD5-E930-427F-99EF-3787EC0F31B2@gmail.com> (message from Yuan Fu on Fri, 20 Dec 2024 00:25:23 -0800)
> From: Yuan Fu <casouri@gmail.com>
> Date: Fri, 20 Dec 2024 00:25:23 -0800
> Cc: Eli Zaretskii <eliz@gnu.org>,
> 73310@debbugs.gnu.org
>
>
>
> > On Dec 19, 2024, at 1:34 PM, vinurs <hi@vinurs.me> wrote:
> >
> > Hi,
> > I tried version 0.25.0, and using the same method it doesn't always reproduce the issue, but it still hangs. On the same line, if I repeatedly delete and press space, it also hangs. I just haven't found a consistent way to reproduce it yet.
>
> Thanks. That’s bad news. I’ll also see if I can modify my C program to reproduce this.
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.
next prev parent reply other threads:[~2024-12-20 8:37 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 [this message]
2024-12-20 9:14 ` Yuan Fu
2024-12-20 12:15 ` Eli Zaretskii
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=86msgqagxq.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).