From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Daniel Colascione <dancol@dancol.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: (heap 1024 82721 1933216)
Date: Sat, 18 Jan 2014 23:19:02 -0500 [thread overview]
Message-ID: <jwv7g9wfw0i.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <52DB472B.5060805@dancol.org> (Daniel Colascione's message of "Sat, 18 Jan 2014 19:31:55 -0800")
>> Could be. For an Emacs that grew to 6GB, I don't find it worrisome
>> if it doesn't shrink back below 2GB.
[...]
> Longer-term, it would be nice to be able to compact objects. We could move
> objects during the unmark phase of GC by looking for forwarding pointers to
> new object locations. (Of course, objects found through conservative
> scanning would have to be considered pinned.)
Lots of work for *very* little benefit. I've pretty much never seen
a case where a user is really annoyed just by Emacs's size "after
freeing everything". In pretty much all cases, the user was already
annoyed at Emacs's size *before* freeing everything, so that's the
problem to solve. Once this problem is solved, the fact that the memory
is not very much returned to the OS is usually not a problem any more.
>> I'm much more worried about: how on earth did it grow to 6GB?
> I have no idea --- I was just doing normal editing over a few dozen files.
Yet, *that* is the problem. The fact that freeing everything didn't let
you work around this problem is of very little concern.
So if you ever bump into such a situation, don't bother trying to free
stuff, and instead try and figure out what is eating all that memory.
Stefan
next prev parent reply other threads:[~2014-01-19 4:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 13:39 (heap 1024 82721 1933216) Daniel Colascione
2014-01-18 13:50 ` Eli Zaretskii
2014-01-18 13:51 ` Daniel Colascione
2014-01-18 14:07 ` Eli Zaretskii
2014-01-18 14:12 ` Daniel Colascione
2014-01-18 17:17 ` Eli Zaretskii
2014-01-18 14:15 ` David Kastrup
2014-01-18 17:19 ` Eli Zaretskii
2014-01-19 2:53 ` Stefan Monnier
2014-01-19 3:31 ` Daniel Colascione
2014-01-19 4:19 ` Stefan Monnier [this message]
2014-01-19 4:24 ` Daniel Colascione
2014-01-19 14:37 ` Stefan Monnier
2014-01-19 15:45 ` 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=jwv7g9wfw0i.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dancol@dancol.org \
--cc=emacs-devel@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).