From: "Basil L. Contovounesios" <basil@contovou.net>
To: Yuan Fu <casouri@gmail.com>
Cc: 71012@debbugs.gnu.org, eller.helmut@gmail.com
Subject: bug#71012: 30.0.50; tree-sitter crash
Date: Thu, 13 Jun 2024 13:43:23 +0200 [thread overview]
Message-ID: <87r0d12hlw.fsf@epfl.ch> (raw)
In-Reply-To: <C61DD1E2-375B-4029-B990-89193BB54C08@gmail.com> (Yuan Fu's message of "Tue, 11 Jun 2024 22:38:43 -0700")
Yuan Fu [2024-06-11 22:38 -0700] wrote:
>> On Jun 7, 2024, at 1:39 AM, Basil L. Contovounesios <basil@contovou.net> wrote:
>>
>> Just curious: since generate-new-buffer creates a new buffer each time
>> it is called, is it guaranteed that this buffer will eventually be GCed,
>> once the caller of treesit-parse-string is done with it?
>
> Yeah, from my testing that seems to be the case.
What did you try?
I'm putting the following in an emacs -Q *scratch* buffer:
(require 'treesit)
(message "# of buffers before : %d" (length (buffer-list)))
(dotimes-with-progress-reporter (i 10000) "Parsing"
(treesit-parse-string "int c = 0;" 'c))
(garbage-collect)
(message "# of buffers after : %d" (length (buffer-list)))
Each time I M-x eval-buffer:
- the list of buffers grows
- the memory usage grows
- loop iterations slow down noticeably
Am I missing something?
--
Basil
next prev parent reply other threads:[~2024-06-13 11:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 13:39 bug#71012: 30.0.50; tree-sitter crash Helmut Eller
2024-05-17 15:29 ` Eli Zaretskii
2024-05-17 15:34 ` Helmut Eller
2024-05-17 16:00 ` Eli Zaretskii
2024-05-18 6:07 ` Yuan Fu
2024-05-27 22:10 ` Yuan Fu
2024-05-29 5:15 ` Yuan Fu
2024-05-29 12:28 ` Eli Zaretskii
2024-06-01 17:15 ` Yuan Fu
2024-06-01 17:43 ` Yuan Fu
2024-06-06 5:31 ` Yuan Fu
2024-06-07 8:39 ` Basil L. Contovounesios
2024-06-10 8:12 ` Basil L. Contovounesios
2024-06-10 18:25 ` Eli Zaretskii
2024-06-12 5:38 ` Yuan Fu
2024-06-12 5:38 ` Yuan Fu
2024-06-13 11:43 ` Basil L. Contovounesios [this message]
2024-06-13 11:53 ` Basil L. Contovounesios
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=87r0d12hlw.fsf@epfl.ch \
--to=basil@contovou.net \
--cc=71012@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eller.helmut@gmail.com \
/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).