From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Is with-temp-buffer really temporary?
Date: Tue, 27 Apr 2021 12:49:12 -0400 [thread overview]
Message-ID: <jwveeevn0js.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 20210427071122.GA7836@tuxteam.de
>> > And if Emacs exits, finishes the process, is memory then scraped?
>> Of course not.
> I'd think this is your operating system's job.
Also, given the way computers are currently implemented, the cost of
having to scrape all memory immediately after use would be somewhat
high, especially compared to the benefit:
- most of that memory contains data of no significance, so most of that
work is wasted.
- it just removes one particular attack vector, among many others, so
the added security gain is low.
Stefan
next prev parent reply other threads:[~2021-04-27 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 17:51 Is with-temp-buffer really temporary? Jean Louis
2021-04-26 19:58 ` Stefan Monnier
2021-04-26 20:53 ` Jean Louis
2021-04-26 22:42 ` Stefan Monnier
2021-04-27 7:11 ` tomas
2021-04-27 16:49 ` Stefan Monnier [this message]
2021-04-27 17:39 ` Jean Louis
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=jwveeevn0js.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).