GNU logs - #60653, boring messages

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#60653: 30.0.50; tree-sitter: `treesit-[explore/inspect]-mode' can leak memory
Resent-From: Mickey Petersen <mickey@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Sun, 08 Jan 2023 10:46:02 +0000
Resent-Message-ID: <handler.60653.B.167317470314713 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 60653 <at> debbugs.gnu.org
Received-SPF: Pass (protection.outlook.com: domain of masteringemacs.org
 designates 178.79.136.144 as permitted sender)
 receiver=protection.outlook.com; client-ip=178.79.136.144;
 helo=semantical.co.uk; pr=C
From: Mickey Petersen <mickey@HIDDEN>
Date: Sun, 08 Jan 2023 10:44:44 +0000
Message-ID: <87wn5xjof7.fsf@HIDDEN>
Content-Type: text/plain
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 Jan 2023 10:44:46.5601 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 54f531a0-1581-467f-00de-08daf1655c22
X-MS-Exchange-CrossTenant-Id: a4e27e3d-bab0-45e8-8942-e64cf9fbd34f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=a4e27e3d-bab0-45e8-8942-e64cf9fbd34f; Ip=[178.79.136.144];
 Helo=[semantical.co.uk]
X-MS-Exchange-CrossTenant-AuthSource: LO2GBR01FT032.eop-gbr01.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LO0P265MB5191
Received-SPF: pass client-ip=40.107.11.122;
 envelope-from=mickey@HIDDEN;
 helo=GBR01-CWL-obe.outbound.protection.outlook.com
X-Spam_score_int: -20
X-Spam_score: -2.1
X-Spam_bar: --
X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
 RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001,
 SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Spam-Score: -1.4 (-)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -2.4 (--)


If you enable either the `treesit-inspect-mode' or `treesit-explore-mode' and leave them to their devices, you may find that through excessive editing, particularly programmatically, that it can cause memory leaks over time.

I am 90% certain those modes are responsible: if I do not use them, then I do not experience these issues. I have had the oomkiller reap the Emacs process as it simply balloons out of control over time.





In GNU Emacs 30.0.50 (build 6, x86_64-pc-linux-gnu, GTK+ Version
 3.24.20, cairo version 1.16.0) of 2023-01-02 built on mickey-work
Repository revision: c209802f7b3721a1b95113290934a23fee88f678
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12013000
System Description: Ubuntu 20.04.3 LTS

Configured using:
 'configure --with-native-compilation --with-json --with-mailutils
 --without-compress-install --with-imagemagick CC=gcc-10'

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Mickey Petersen <mickey@HIDDEN>
Subject: bug#60653: Acknowledgement (30.0.50; tree-sitter: `treesit-[explore/inspect]-mode'
 can leak memory)
Message-ID: <handler.60653.B.167317470314713.ack <at> debbugs.gnu.org>
References: <87wn5xjof7.fsf@HIDDEN>
X-Gnu-PR-Message: ack 60653
X-Gnu-PR-Package: emacs
Reply-To: 60653 <at> debbugs.gnu.org
Date: Sun, 08 Jan 2023 10:46:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-gnu-emacs@HIDDEN

If you wish to submit further information on this problem, please
send it to 60653 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
60653: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D60653
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#60653: 30.0.50; tree-sitter:  `treesit-[explore/inspect]-mode' can leak memory
References: <87wn5xjof7.fsf@HIDDEN>
In-Reply-To: <87wn5xjof7.fsf@HIDDEN>
Resent-From: Yuan Fu <casouri@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Mon, 09 Jan 2023 03:39:02 +0000
Resent-Message-ID: <handler.60653.B60653.16732355384512 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Mickey Petersen <mickey@HIDDEN>
Cc: 60653 <at> debbugs.gnu.org
From: Yuan Fu <casouri@HIDDEN>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Message-Id: <4B554554-60E0-416A-9F3E-CC704B79CDEC@HIDDEN>
Date: Sun, 8 Jan 2023 19:38:49 -0800
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>


Mickey Petersen <mickey@HIDDEN> writes:

> If you enable either the `treesit-inspect-mode' or
> `treesit-explore-mode' and leave them to their devices, you may find
> that through excessive editing, particularly programmatically, that it
> can cause memory leaks over time.
>
> I am 90% certain those modes are responsible: if I do not use them,
> then I do not experience these issues. I have had the oomkiller reap
> the Emacs process as it simply balloons out of control over time.

Hmmm, maybe it=E2=80=99s just using a lot of memory. Emacs never returns =
memory
once it allocates them. Are you opening a lot of buffers? A tree-sitter
parse tree uses about 10x memory as the source text.

Yuan

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#60653: 30.0.50; tree-sitter: `treesit-[explore/inspect]-mode' can leak memory
Resent-From: Mickey Petersen <mickey@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Mon, 09 Jan 2023 09:02:02 +0000
Resent-Message-ID: <handler.60653.B60653.167325487823581 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Yuan Fu <casouri@HIDDEN>
Cc: 60653 <at> debbugs.gnu.org
Received-SPF: Pass (protection.outlook.com: domain of masteringemacs.org
 designates 178.79.136.144 as permitted sender)
 receiver=protection.outlook.com; client-ip=178.79.136.144;
 helo=semantical.co.uk; pr=C
References: <4B554554-60E0-416A-9F3E-CC704B79CDEC@HIDDEN>
User-agent: mu4e @VERSION@; emacs 30.0.50
From: Mickey Petersen <mickey@HIDDEN>
Date: Mon, 09 Jan 2023 08:58:50 +0000
Organization: Mastering Emacs
In-reply-to: <4B554554-60E0-416A-9F3E-CC704B79CDEC@HIDDEN>
Message-ID: <87v8lghyjz.fsf@HIDDEN>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Jan 2023 09:01:08.0650 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 3316bcb9-5b05-4b5f-b646-08daf2200c08
X-MS-Exchange-CrossTenant-Id: a4e27e3d-bab0-45e8-8942-e64cf9fbd34f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=a4e27e3d-bab0-45e8-8942-e64cf9fbd34f; Ip=[178.79.136.144];
 Helo=[semantical.co.uk]
X-MS-Exchange-CrossTenant-AuthSource: CWLGBR01FT042.eop-gbr01.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LO0P265MB6947
X-Spam-Score: -0.0 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)


Yuan Fu <casouri@HIDDEN> writes:

> Mickey Petersen <mickey@HIDDEN> writes:
>
>> If you enable either the `treesit-inspect-mode' or
>> `treesit-explore-mode' and leave them to their devices, you may find
>> that through excessive editing, particularly programmatically, that it
>> can cause memory leaks over time.
>>
>> I am 90% certain those modes are responsible: if I do not use them,
>> then I do not experience these issues. I have had the oomkiller reap
>> the Emacs process as it simply balloons out of control over time.
>
> Hmmm, maybe it=E2=80=99s just using a lot of memory. Emacs never returns =
memory
> once it allocates them. Are you opening a lot of buffers? A tree-sitter
> parse tree uses about 10x memory as the source text.
>

Nah. This VM's got 64 GiB RAM. So that's not it. And my list of open
buffers does go up or down a bit, but as I'm working on TS stuff, it's
mostly the same handful of smallish files.

Note that I used the third-party tree-sitter implementation for a long
time and never encountered this. And it never seems to happen if I
leave the explorer/inspect mode off. Note that I do do a lot of repeat
editing in the ones that have those modes active.

There's definitely something going on here, and I wish I had more
information to give you, Yuan!

> Yuan

Message sent to bug-gnu-emacs@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#60653: 30.0.50; tree-sitter:  `treesit-[explore/inspect]-mode' can leak memory
References: <87wn5xjof7.fsf@HIDDEN>
In-Reply-To: <87wn5xjof7.fsf@HIDDEN>
Resent-From: Yuan Fu <casouri@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Tue, 10 Jan 2023 03:46:01 +0000
Resent-Message-ID: <handler.60653.B60653.167332232321782 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 60653
X-GNU-PR-Package: emacs
X-GNU-PR-Keywords: 
To: Mickey Petersen <mickey@HIDDEN>
Cc: 60653 <at> debbugs.gnu.org
Received: via spool by 60653-submit <at> debbugs.gnu.org id=B60653.167332232321782
          (code B ref 60653); Tue, 10 Jan 2023 03:46:01 +0000
Received: (at 60653) by debbugs.gnu.org; 10 Jan 2023 03:45:23 +0000
Received: from localhost ([127.0.0.1]:38463 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1pF5Zj-0005fG-2y
	for submit <at> debbugs.gnu.org; Mon, 09 Jan 2023 22:45:23 -0500
Received: from mail-pl1-f182.google.com ([209.85.214.182]:36426)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <casouri@HIDDEN>) id 1pF5Zi-0005ez-56
 for 60653 <at> debbugs.gnu.org; Mon, 09 Jan 2023 22:45:22 -0500
Received: by mail-pl1-f182.google.com with SMTP id w3so11853227ply.3
 for <60653 <at> debbugs.gnu.org>; Mon, 09 Jan 2023 19:45:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=to:cc:date:message-id:subject:mime-version
 :content-transfer-encoding:from:from:to:cc:subject:date:message-id
 :reply-to; bh=gaDyqLJIpWEZjZ38VC59PWEDZGpSQDmNlZjzG5eI3Sg=;
 b=eMbtfr38e3rjHuiWq8FJ/bRHoi9OS/YzelUv/oub30rc2yBwpWYCEAPIY0u/pcfgNb
 RKXvo1sF0dQ8uFgu8BCxyeYhAujykoW3etgUQ61tFsg/Dzq5rU5L8m+s4vr2iAytronE
 lnIF7XApRVDObOsqmYFcZcBDW/NPAP1taKiSYmBawpnxX8GmWfFTlbOalvCQSNp6qyAb
 w8EecHeVGt+cAsa2X/5JkeFekHx9y3XehsNirXyTwqxvRgw+w1PnFnEF+Bo9a6uKJfCs
 /zjZU+1sfUDymXUmYzf6sEkJ6uyW6gNQP6YxkbErq3ZwU/u5H0caE6w8iTdMf57gg7m7
 QZMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=to:cc:date:message-id:subject:mime-version
 :content-transfer-encoding:from:x-gm-message-state:from:to:cc
 :subject:date:message-id:reply-to;
 bh=gaDyqLJIpWEZjZ38VC59PWEDZGpSQDmNlZjzG5eI3Sg=;
 b=FRjCni+SwYB7oKvHb0evaDQqQNhGUCFcucElEHEApD2e1J3MjFMchcoSFej9yKyR48
 dW1csutr6TDr5xIwBicVVTf1LZRFVnvNkxmDyFc/zRQAEMEn6jkDFIjwiA9RJ3Mw2z0L
 FwwxRo+TZcTW6o75KP8KBt2r8fWY8XrXnES+elq8gmzAzlatDlgOtjx9cNS7jgffRnUC
 PRG580Scw5FZxSzyjIFm43ROW1ERonEXATrn41M66/52HQg3CwBnvJtrzZRNI7RLjUZT
 +HbebG7mLLXG6aiazkko2unE9Mi/Jd2rGSoDRkELqol/9uHEWL4bQcq90Q/NVjowZyN7
 z1jg==
X-Gm-Message-State: AFqh2krloiRdKYV8smY+4JO83rWrSyKLoGNditY3i3bqHIDX7FfURIdT
 yENN8faY82xrwj0cxP8AWz0=
X-Google-Smtp-Source: AMrXdXvSUhyZQbDs+NB3PdAP8cbRxldcXP2FLLzvrS1HUkiu3RPdi+IUJ8W+kSlIVt4iZh/OiO+Y2Q==
X-Received: by 2002:a05:6a20:2a07:b0:af:6d54:239a with SMTP id
 e7-20020a056a202a0700b000af6d54239amr96383155pzh.38.1673322316012; 
 Mon, 09 Jan 2023 19:45:16 -0800 (PST)
Received: from smtpclient.apple (cpe-172-117-161-177.socal.res.rr.com.
 [172.117.161.177]) by smtp.gmail.com with ESMTPSA id
 t23-20020aa79477000000b00574e84ed847sm6858966pfq.24.2023.01.09.19.45.15
 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
 Mon, 09 Jan 2023 19:45:15 -0800 (PST)
From: Yuan Fu <casouri@HIDDEN>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Message-Id: <6478F5E8-495A-4ADD-BCB4-7062260938D8@HIDDEN>
Date: Mon, 9 Jan 2023 19:45:14 -0800
X-Mailer: Apple Mail (2.3696.120.41.1.1)
X-Spam-Score: 0.0 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)


Mickey Petersen <mickey@HIDDEN> writes:

> Yuan Fu <casouri@HIDDEN> writes:
>
>> Mickey Petersen <mickey@HIDDEN> writes:
>>
>>> If you enable either the `treesit-inspect-mode' or
>>> `treesit-explore-mode' and leave them to their devices, you may find
>>> that through excessive editing, particularly programmatically, that =
it
>>> can cause memory leaks over time.
>>>
>>> I am 90% certain those modes are responsible: if I do not use them,
>>> then I do not experience these issues. I have had the oomkiller reap
>>> the Emacs process as it simply balloons out of control over time.
>>
>> Hmmm, maybe it=E2=80=99s just using a lot of memory. Emacs never =
returns memory
>> once it allocates them. Are you opening a lot of buffers? A =
tree-sitter
>> parse tree uses about 10x memory as the source text.
>>
>
> Nah. This VM's got 64 GiB RAM. So that's not it. And my list of open
> buffers does go up or down a bit, but as I'm working on TS stuff, it's
> mostly the same handful of smallish files.
>
> Note that I used the third-party tree-sitter implementation for a long
> time and never encountered this. And it never seems to happen if I
> leave the explorer/inspect mode off. Note that I do do a lot of repeat
> editing in the ones that have those modes active.
>
> There's definitely something going on here, and I wish I had more
> information to give you, Yuan!

Thank you. I=E2=80=99ll try to figure it out! At this point my guess is =
that
there=E2=80=99s some leak in the C code which is triggered a lot by
treesit-explore-mode.

Yuan

Message sent to bug-gnu-emacs@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#60653: 30.0.50; tree-sitter:  `treesit-[explore/inspect]-mode' can leak memory
References: <87wn5xjof7.fsf@HIDDEN>
In-Reply-To: <87wn5xjof7.fsf@HIDDEN>
Resent-From: Yuan Fu <casouri@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Tue, 17 Jan 2023 09:40:02 +0000
Resent-Message-ID: <handler.60653.B60653.16739483493071 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 60653
X-GNU-PR-Package: emacs
X-GNU-PR-Keywords: 
To: Mickey Petersen <mickey@HIDDEN>
Cc: 60653 <at> debbugs.gnu.org
Received: via spool by 60653-submit <at> debbugs.gnu.org id=B60653.16739483493071
          (code B ref 60653); Tue, 17 Jan 2023 09:40:02 +0000
Received: (at 60653) by debbugs.gnu.org; 17 Jan 2023 09:39:09 +0000
Received: from localhost ([127.0.0.1]:35790 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1pHiQv-0000nT-EV
	for submit <at> debbugs.gnu.org; Tue, 17 Jan 2023 04:39:09 -0500
Received: from mail-pj1-f44.google.com ([209.85.216.44]:53184)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <casouri@HIDDEN>) id 1pHiQt-0000n9-Jy
 for 60653 <at> debbugs.gnu.org; Tue, 17 Jan 2023 04:39:08 -0500
Received: by mail-pj1-f44.google.com with SMTP id o13so28281885pjg.2
 for <60653 <at> debbugs.gnu.org>; Tue, 17 Jan 2023 01:39:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=to:cc:date:message-id:subject:mime-version
 :content-transfer-encoding:from:from:to:cc:subject:date:message-id
 :reply-to; bh=hw/S2GwK4yzSCt9jrMyBTrBL6DocwAl+SFBLwBFauso=;
 b=hdl66AaGgYHfWCw6Fcd4EsxIGFMIy6OkSsOzieqPOwVQ+ZHM6FE2+mHs/hbUYorVcm
 vg2arjKdWSYDBt3g/nQAlhzjJF3O0fXGLKi011+VofomtYlIuGtw6dAtbR/Lw6DWdDxt
 HI8Fimol/HnF3r+XIT0gLaNceXNboVNLBKtSA4MmgbF0AuRabqSfqmvUxgzNZXdcdIWZ
 2h80JiAs21Jco04GWB4sYLkm8q/z4kR6N/MDVQMgOcLjxCncYx8WHK8su9XAURmE24+o
 NQoAWW81cqRuEOXmHrunQXgJ/G6/UlaqX5iJqaCUvTETALREggxr5eueLfBXiMntAYbH
 D5gA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=to:cc:date:message-id:subject:mime-version
 :content-transfer-encoding:from:x-gm-message-state:from:to:cc
 :subject:date:message-id:reply-to;
 bh=hw/S2GwK4yzSCt9jrMyBTrBL6DocwAl+SFBLwBFauso=;
 b=mRfR8J38gbf3xcW9vLMGsRr1BUXSvlOkbAG0cG/p1mraAfIn9N1tB1A0KsSrfRK6wf
 cHMJWJe7PA7FrNH6hpKJN7roMpSkzMSQKuMLm/gMlXMrINSQjSctqeSFS+xhiiXtCR9f
 kxtwAJfU6CcbEr97BcfzCrkrlRxfN60LdzGPgIHgQ15SKGnqDFG0MX/miWGnu66psugc
 lL2dUH1q/LgQqpgcc36TD8pvBo769fSD58K9TOJq8ZJQ3UstKpnNvj2y8LURQFp/2gSB
 5ixiL59Q5Dc+KnsBXjkKh7ArMbVfeOYADxCWkommnbhWHHHw6ohNSgmJ4cbO32ZFk8w1
 b38g==
X-Gm-Message-State: AFqh2kol8SHID8gJ+Jya10oF+IASxLfhd14VKUl+U0HvKGNtKM5dpBgb
 mUoMisxYvUcIr+dspLVb5T0tj+Ywr2w=
X-Google-Smtp-Source: AMrXdXsyGUygTlgQNcQJUhMj5uX5XHiOixE6DnazLFvHjNVFOEGh8ssnvPJSuenyvcRaEe1O3whJfg==
X-Received: by 2002:a17:902:6b4b:b0:194:a1f6:65b6 with SMTP id
 g11-20020a1709026b4b00b00194a1f665b6mr3452231plt.41.1673948341885; 
 Tue, 17 Jan 2023 01:39:01 -0800 (PST)
Received: from smtpclient.apple (cpe-172-117-161-177.socal.res.rr.com.
 [172.117.161.177]) by smtp.gmail.com with ESMTPSA id
 a14-20020a170902710e00b00194516b2d88sm11466446pll.260.2023.01.17.01.39.01
 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
 Tue, 17 Jan 2023 01:39:01 -0800 (PST)
From: Yuan Fu <casouri@HIDDEN>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Message-Id: <343B471A-78B0-4DEC-90B4-2B6283941F1A@HIDDEN>
Date: Tue, 17 Jan 2023 01:39:00 -0800
X-Mailer: Apple Mail (2.3696.120.41.1.1)
X-Spam-Score: 0.0 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)


Yuan Fu <casouri@HIDDEN> writes:

> Mickey Petersen <mickey@HIDDEN> writes:
>
>> Yuan Fu <casouri@HIDDEN> writes:
>>
>>> Mickey Petersen <mickey@HIDDEN> writes:
>>>
>>>> If you enable either the `treesit-inspect-mode' or
>>>> `treesit-explore-mode' and leave them to their devices, you may =
find
>>>> that through excessive editing, particularly programmatically, that =
it
>>>> can cause memory leaks over time.
>>>>
>>>> I am 90% certain those modes are responsible: if I do not use them,
>>>> then I do not experience these issues. I have had the oomkiller =
reap
>>>> the Emacs process as it simply balloons out of control over time.
>>>
>>> Hmmm, maybe it=E2=80=99s just using a lot of memory. Emacs never =
returns memory
>>> once it allocates them. Are you opening a lot of buffers? A =
tree-sitter
>>> parse tree uses about 10x memory as the source text.
>>>
>>
>> Nah. This VM's got 64 GiB RAM. So that's not it. And my list of open
>> buffers does go up or down a bit, but as I'm working on TS stuff, =
it's
>> mostly the same handful of smallish files.
>>
>> Note that I used the third-party tree-sitter implementation for a =
long
>> time and never encountered this. And it never seems to happen if I
>> leave the explorer/inspect mode off. Note that I do do a lot of =
repeat
>> editing in the ones that have those modes active.
>>
>> There's definitely something going on here, and I wish I had more
>> information to give you, Yuan!
>
> Thank you. I=E2=80=99ll try to figure it out! At this point my guess =
is that
> there=E2=80=99s some leak in the C code which is triggered a lot by
> treesit-explore-mode.

When you observe the memory leak, do you see warnings mentioning pure
storage, etc? I=E2=80=99m asking because we just fixed a bug that =
overflows the
pure space which may or may not be the same bug as this one.

Yuan

Last modified: Tue, 17 Jan 2023 09:45:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.