From: Eli Zaretskii <eliz@gnu.org>
To: "Alex McGrath" <amk@amk.ie>
Cc: 67129@debbugs.gnu.org
Subject: bug#67129: 30.0.50; starting js-mode or js-ts-mode eats ram until emacs gets killed
Date: Sun, 12 Nov 2023 18:31:33 +0200 [thread overview]
Message-ID: <834jhrue56.fsf@gnu.org> (raw)
In-Reply-To: <763263638564761f33298eb3626520794d71aa96@amk.ie>
[Please use Reply All to keep the bug tracker on the CC list.]
> Date: Sun, 12 Nov 2023 13:09:26 +0000
> From: "Alex McGrath" <amk@amk.ie>
> TLS-Required: No
>
> 12 November 2023 at 12:32, "Eli Zaretskii" <eliz@gnu.org> wrote:
> >
> > If you mean this recipe:
> >
> > emacs -Q
> > M-x js-mode RET
> >
> > then after it I cannot see any changes in the Emacs's memory
> > footprint. It stays constant. Do I need to do something else, like
> > visit a JS source file?
> >
>
> Yes this is the recipe i used, I've debugged it a bit more, and I
> think its an issue with how the javascript tree-sitter grammer
> is built on alpine, if its not installed it works okay, and if its
> installed via treesit-install-language-grammer it also works fine.
So the problem is only with js-ts-mode, not with js-mode? Your
original report said both modes cause the problem. js-mode doesn't
use the tree-sitter grammar.
> I think this can be closed as it seems specific to something alpine
> is doing
Fine by me, but I'd like first to hear from you that js-mode is free
from the problem, otherwise the tree-sitter grammar is not necessarily
the cause.
prev parent reply other threads:[~2023-11-12 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 12:24 bug#67129: 30.0.50; starting js-mode or js-ts-mode eats ram until emacs gets killed alex via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-12 12:32 ` Eli Zaretskii
[not found] ` <763263638564761f33298eb3626520794d71aa96@amk.ie>
2023-11-12 16:31 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834jhrue56.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67129@debbugs.gnu.org \
--cc=amk@amk.ie \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.