From: Arthur Miller <arthur.miller@live.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to debug memory leaks
Date: Fri, 26 Mar 2021 16:53:58 +0100 [thread overview]
Message-ID: <AM9PR09MB497729BAB13C83C50C2E645C96619@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <83k0puorpb.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 26 Mar 2021 18:33:20 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Arthur Miller <arthur.miller@live.com>
>> Cc: help-gnu-emacs@gnu.org
>> Date: Fri, 26 Mar 2021 16:09:33 +0100
>>
>> > That's what GC does.
>> Yes, but GC can't know if I don't need undo history, right
>
> And neither do you. GC compacts the undo history, though, and frees
> the slack.
Ok, good if GC compacts the undo, but I could explicitly wish/know
sometimes that I could "freeze" the undo. I could just put on my own
interactive command that does this instead of using
M-: (setq buffer-undo-list nil), but there could be some other stuff
based on mode, like eshell or term or I don't know what. That could help
GC.
>> or old text in eshell buffer?
>
> Delete it, and it will be free'd.
Yes, so that is what I am saying; a hook to put all kind of various
"delete" stuff for various modes so we can run interactive command, say
"clean-buffer" or whatever, and it will run the apropriate "deletes" and
maybe other stuff based on mode.
>> Can we maybe get a "cleanup-hook" so we can specify per mode which
>> data/variables shoudl be set to nil so GC can do it's job?
>
> It's much easier to delete unneeded stuff, and let GC recycle the
> memory.
:-). Yes that is exactly what I ask for; a hook where we could put what
will be deleted and that will be called on user request interactively.
Just as a note: no idea if you have found the memory leak or not, the
big one that everyone was repporting few weeks ago, but I haven't
experienced any leaks or slugishness with lately builds. I guess you
found it? :).
next prev parent reply other threads:[~2021-03-26 15:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 5:29 How to debug memory leaks edgar
2021-03-25 14:23 ` Stefan Monnier
2021-03-25 15:01 ` Jean Louis
2021-03-25 15:18 ` Stefan Monnier
2021-03-25 20:15 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-25 17:54 ` edgar
2021-03-25 18:26 ` Stefan Monnier
2021-03-25 19:38 ` Jean Louis
2021-03-25 22:24 ` edgar
2021-03-26 5:48 ` Robert Thorpe
2021-03-26 5:58 ` edgar
2021-03-26 14:11 ` Stefan Monnier
2021-03-26 14:17 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 14:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 14:57 ` Arthur Miller
2021-03-26 15:02 ` Eli Zaretskii
2021-03-26 15:09 ` Arthur Miller
2021-03-26 15:33 ` Eli Zaretskii
2021-03-26 15:53 ` Arthur Miller [this message]
2021-03-26 16:03 ` Eli Zaretskii
2021-03-26 16:11 ` Arthur Miller
2021-03-26 16:25 ` Stefan Monnier
2021-03-26 16:32 ` Arthur Miller
2021-03-26 16:44 ` Stefan Monnier
2021-03-26 18:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 18:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-27 8:20 ` Arthur Miller
2021-03-27 15:03 ` Stefan Monnier
2021-03-27 15:13 ` Arthur Miller
2021-03-27 15:30 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 15:10 ` boost interactive feel speed (was: Re: How to debug memory leaks) Emanuel Berg via Users list for the GNU Emacs text editor
-- strict thread matches above, loose matches on Subject: below --
2021-03-25 22:21 How to debug memory leaks edgar
2021-03-21 18:17 edgar
2021-03-21 18:25 ` 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=AM9PR09MB497729BAB13C83C50C2E645C96619@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=eliz@gnu.org \
--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).