From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60255@debbugs.gnu.org, Ryan Wilson <ryan.wilson@everlaw.com>
Subject: bug#60255: Memory Leak
Date: Mon, 4 Sep 2023 12:53:52 -0700 [thread overview]
Message-ID: <CADwFkmmKTAsK0XN52vKG3ppyR3-57qOcYTGtGMc_N5NQmiJVkQ@mail.gmail.com> (raw)
In-Reply-To: <83r0wr900v.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 22 Dec 2022 12:59:44 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Wed, 21 Dec 2022 18:48:02 -0800
>> From: Ryan Wilson via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> I am just using emacs normally, mostly for typescript development, so
>> that might be the offending mode. Emacs is currently using 1.7GB of
>> memory, the other day I killed it after I saw it was using 19.9GB. I ran
>> memory report and nothing was reported as using significant memory.
>>
>> Memory report output
>
> It could be that a large part of memory that is mapped into the Emacs
> process is actually free, and glibc keeps it because it cannot release
> it to the system for some reason.
>
> When you get a significantly larger memory footprint again, please
> invoke the function 'malloc-info', and post here everything it writes
> to stderr stream. The data this produces will show how much memory is
> actually in use.
Ryan, it seems like we need more information here to make any progress.
Are you still seeing this? If yes, did you have a chance to look into
this any further?
next prev parent reply other threads:[~2023-09-04 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 2:48 bug#60255: Memory Leak Ryan Wilson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-22 10:59 ` Eli Zaretskii
2023-09-04 19:53 ` Stefan Kangas [this message]
2024-01-10 10:47 ` Stefan Kangas
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=CADwFkmmKTAsK0XN52vKG3ppyR3-57qOcYTGtGMc_N5NQmiJVkQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=60255@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ryan.wilson@everlaw.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).