From: Carsten Mattner <carstenmattner@googlemail.com>
To: Chong Yidong <cyd@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Update on the Emacs release schedule?
Date: Sat, 7 Jan 2012 12:02:59 +0100 [thread overview]
Message-ID: <CACY+HvqauT4HcG3sN-67WydkCF-jhH8zRDv+1VPiQJQ_bps7gg@mail.gmail.com> (raw)
In-Reply-To: <87vcookmxd.fsf@gnu.org>
On Sat, Jan 7, 2012 at 8:10 AM, Chong Yidong <cyd@gnu.org> wrote:
> As for the code, there are still a number of issues that need more
> attention, most prominently the mysterious memory leak(s) that may or
> may not involve Gnus and/or GnuTLS and/or Mac OS X.
For the record, I use a --without-gnutls Emacs while also not
using Gnus, and am part of the users seeing the "leaks".
Ready to test any patch or memory statistics collector background
scripts for analysis.
Still running debug builds of Emacs just in case there's another crash.
No other crash seen so far, but I've enabled Ido just recently, and
have to use it more extensively before I can be reasonably sure it
might be solved.
Reading Tom Tromey's recent blog post, I'd say any improvements
to the allocator and/or collector will be a huge NEWS entry for 24.
next prev parent reply other threads:[~2012-01-07 11:02 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 [this message]
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
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=CACY+HvqauT4HcG3sN-67WydkCF-jhH8zRDv+1VPiQJQ_bps7gg@mail.gmail.com \
--to=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).