From: Madhu <enometh@meer.net>
To: help-gnu-emacs@gnu.org
Subject: Re: memory leaks
Date: Sun, 06 Mar 2022 16:29:41 +0530 [thread overview]
Message-ID: <m35yor1h42.fsf@leonis4.robolove.meer.net> (raw)
In-Reply-To: 83ee3ihs17.fsf@gnu.org
* Eli Zaretskii <83ee3ihs17.fsf@gnu.org> :
Wrote on Fri, 04 Mar 2022 13:32:36 +0200:
> This was already discussed in that bug, and you said back then that
> when the shell buffer is killed, the memory is freed up. So how come
> you now say this is still a bug, and what is the difference between
> the case discussed in that bug and what you describe now?
That message was from nov 2020. It is a duplicate
I onky authorized gmane to send my message this week to emacs-help,
looks like I had a bunch of messages posted through gmane over the years
which were not posted by gmane because i was not authorized, which have
now been delivered, but which were kept in hold. I think in most cases i
posted the messages outside of gmane.
sorry for the noise
I've not seen the memory "leaks" recently. Maybe I stopped using the
packages that triggered them
next prev parent reply other threads:[~2022-03-06 10:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 7:23 memory leaks Madhu
2019-09-20 8:00 ` Jean-Christophe Helary
2019-09-20 8:11 ` Eli Zaretskii
[not found] ` <mailman.572.1568967069.2190.help-gnu-emacs@gnu.org>
2019-09-20 8:31 ` Madhu
2019-09-20 9:21 ` Eli Zaretskii
[not found] ` <mailman.578.1568971399.2190.help-gnu-emacs@gnu.org>
2020-09-12 13:02 ` Madhu
2020-09-12 13:39 ` Eli Zaretskii
2020-09-12 13:55 ` Michael Heerdegen
2020-09-12 14:09 ` Eli Zaretskii
2020-09-12 19:14 ` Igor Sosa Mayor
2020-09-12 19:26 ` Eli Zaretskii
2020-09-12 19:28 ` Igor Sosa Mayor
2020-09-13 2:30 ` Eli Zaretskii
2020-09-13 3:17 ` Madhu
2020-09-13 14:14 ` Eli Zaretskii
2021-01-21 9:28 ` Madhu
2020-09-13 20:14 ` Stefan Monnier
2020-09-14 10:06 ` Madhu
2020-11-09 17:50 ` Madhu
2022-03-04 11:32 ` Eli Zaretskii
2022-03-06 10:59 ` Madhu [this message]
2022-03-06 11:15 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2020-11-10 1:24 Madhu
2020-11-10 15:16 ` Eli Zaretskii
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=m35yor1h42.fsf@leonis4.robolove.meer.net \
--to=enometh@meer.net \
--cc=help-gnu-emacs@gnu.org \
/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.
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).