From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Carsten Mattner <carstenmattner@googlemail.com>
Cc: Chong Yidong <cyd@gnu.org>, emacs-devel@gnu.org
Subject: Re: Update on the Emacs release schedule?
Date: Sun, 08 Jan 2012 08:54:47 -0500 [thread overview]
Message-ID: <jwvsjjqi9o3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CACY+HvrBOkX6VQpSdjhc9einqLx4yeLoesXtL8frNEhJZd9pQQ@mail.gmail.com> (Carsten Mattner's message of "Sat, 7 Jan 2012 19:32:29 +0100")
>>> For the record, I use a --without-gnutls Emacs while also not
>>> using Gnus, and am part of the users seeing the "leaks".
>> AFAIK you're not seeing leaks, but only excessive memory use (and
>> failure to return memory to the system early enough for your taste),
> Maybe :). How do we define "early enough"? Hours or days?
Never. It's still not necessarily a leak.
A leak is when memory is lost and can never be reused again (short of
restarting Emacs). Whereas IIUC your case is a situation where the
memory is not lost: it will never be returned to the OS but it will be
reused by Emacs itself if/when the occasion shows up.
A leak manifests itself by a memory footprint that keeps on growing
indefinitely even when the usage pattern does not justify any
such increase.
Stefan
next prev parent reply other threads:[~2012-01-08 13:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 4:47 Update on the Emacs release schedule? Lars Magne Ingebrigtsen
2012-01-07 7:10 ` Chong Yidong
2012-01-07 11:02 ` Carsten Mattner
2012-01-07 13:45 ` Ted Zlatanov
2012-01-07 17:02 ` Carsten Mattner
2012-01-07 18:11 ` Stefan Monnier
2012-01-07 18:32 ` Carsten Mattner
2012-01-07 20:13 ` Jan Djärv
2012-01-08 13:54 ` Stefan Monnier [this message]
2012-01-07 13:44 ` fixing memory leaks before the pretest (was: Update on the Emacs release schedule?) Ted Zlatanov
2012-01-07 15:49 ` fixing memory leaks before the pretest Chong Yidong
2012-01-10 0:59 ` Ted Zlatanov
2012-01-07 16:57 ` fixing memory leaks before the pretest (was: Update on the Emacs release schedule?) Carsten Mattner
2012-01-08 2:39 ` YAMAMOTO Mitsuharu
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=jwvsjjqi9o3.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=carstenmattner@googlemail.com \
--cc=cyd@gnu.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).