From: Glenn Morris <rgm@gnu.org>
To: 1053-done@debbugs.gnu.org
Subject: bug#1053: 23.0.60; 600 MB memory not freed after keyboard-quit
Date: Sat, 09 Jul 2011 13:56:26 -0400 [thread overview]
Message-ID: <ejliw772yd.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvej32tntj.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Mon, 29 Sep 2008 21:42:36 -0400")
I don't see a need to keep open this particular report, which was marked
"wontfix" some time ago.
Stefan Monnier wrote:
> Releasing such memory is surprisingly difficult, so you may indeed end
> up with a large Emacs process with a large heap that takes a long time
> to GC, so every time Emacs calls the GC your Emacs appears frozen.
prev parent reply other threads:[~2011-07-09 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 19:20 bug#1053: 23.0.60; 600 MB memory not freed after keyboard-quit Peter Tury
2008-09-30 1:42 ` Stefan Monnier
2011-07-09 17:56 ` Glenn Morris [this message]
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=ejliw772yd.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=1053-done@debbugs.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.
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).