From: Wilhelm Kirschbaum <wkirschbaum@gmail.com>
To: Yuan Fu <casouri@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 72863@debbugs.gnu.org, mail@ssbb.me
Subject: bug#72863: 30.0.50; tree-sitter elixir-ts-mode hangs and memory leak on some elixir and heex code
Date: Wed, 4 Sep 2024 08:39:45 +0200 [thread overview]
Message-ID: <CAOS0-35c3WAZaeHtt_4B3VGJdQynT3ux6cYp9SfYSVoRBJvxWg@mail.gmail.com> (raw)
In-Reply-To: <F19AF072-97D8-48E5-A815-E0E0D37DB6EB@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]
On Thu, Aug 29, 2024 at 8:14 AM Yuan Fu <casouri@gmail.com> wrote:
>
>
> > On Aug 28, 2024, at 10:09 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> >> From: mail@ssbb.me
> >> Date: Thu, 29 Aug 2024 06:57:38 +0400
> >>
> >> Code in attached file cause Emacs to hang and memory leak infinitely
> >> while editing. Try to open this code in elixir-ts-mode and move cursor
> >> on line 6 (between <:loading> </:loading>) and type char by char:
> >>
> >> <.some_component a={
> >>
> >> (for some reason it does not happen with electric-pair-mode when {}
> >> inserted automatically).
> >>
> >> I am able to reproduce this with -Q on few different machines (Linux and
> >> MacOS) and Emacs 29, 30.0.5 and current HEAD.
> >>
> >> C-g does nothing (including with debug-on-quit and sending SIGUSR2)
> >>
> >> At the same time I can't reproduce this in other tree-sitter based
> editors.
> >>
> >> I got this sample code sample from elixir-ts-mode repo but now it's
> moved
> >> to the Emacs core so seems to be out of scope of Github repo issues.
> >>
> >> Attaching samle code and LLDB backtrace.
> >> Also attaching report from built-in MacOS crash reporting tool just in
> case.
> >
> > Thanks.
> >
> > Wilhelm and Yuan, could you please look into this soon?
>
> That’s bizarre, might have some bug around ranges. I’m looking into this.
> Hopefully I can figure it out in a few days :-(
>
> Yuan
I can reproduce the issue by following the above instructions, but need to
do some digging. It only seems to be the case with embedded heex and not
with heex-ts-mode by itself.
WIlhelm
[-- Attachment #2: Type: text/html, Size: 2394 bytes --]
next prev parent reply other threads:[~2024-09-04 6:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 2:57 bug#72863: 30.0.50; tree-sitter elixir-ts-mode hangs and memory leak on some elixir and heex code mail
2024-08-29 5:09 ` Eli Zaretskii
2024-08-29 6:13 ` Wilhelm Kirschbaum
2024-08-29 6:14 ` Yuan Fu
2024-09-04 6:39 ` Wilhelm Kirschbaum [this message]
2024-09-04 7:42 ` mail
2024-09-05 4:32 ` Yuan Fu
2024-09-08 5:44 ` Yuan Fu
2024-09-08 5:54 ` Eli Zaretskii
2024-09-08 5:57 ` Yuan Fu
2024-09-08 7:02 ` Eli Zaretskii
2024-09-08 7:48 ` Yuan Fu
2024-09-11 3:45 ` Yuan Fu
2024-09-11 19:22 ` mail
2024-09-12 7:47 ` Yuan Fu
2024-09-16 6:58 ` Wilhelm Kirschbaum
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=CAOS0-35c3WAZaeHtt_4B3VGJdQynT3ux6cYp9SfYSVoRBJvxWg@mail.gmail.com \
--to=wkirschbaum@gmail.com \
--cc=72863@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=mail@ssbb.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).