From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Carsten Mattner <carstenmattner@googlemail.com>
Cc: Chong Yidong <cyd@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Update on the Emacs release schedule?
Date: Sat, 7 Jan 2012 21:13:39 +0100 [thread overview]
Message-ID: <CF882612-C47C-4E08-B7F4-75AEB174FBF8@swipnet.se> (raw)
In-Reply-To: <CACY+HvrBOkX6VQpSdjhc9einqLx4yeLoesXtL8frNEhJZd9pQQ@mail.gmail.com>
Hello.
7 jan 2012 kl. 19:32 skrev Carsten Mattner <carstenmattner@googlemail.com>:
> On Sat, Jan 7, 2012 at 7:11 PM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>>> 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. AFAIK Osx never gives back memory allocated to the system.
That is why changing malloc implementation might be the only solution.
Jan D.
next prev parent reply other threads:[~2012-01-07 20:13 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 [this message]
2012-01-08 13:54 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CF882612-C47C-4E08-B7F4-75AEB174FBF8@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=carstenmattner@googlemail.com \
--cc=cyd@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.