From: Chong Yidong <cyd@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: fixing memory leaks before the pretest
Date: Sat, 07 Jan 2012 23:49:01 +0800 [thread overview]
Message-ID: <87sjjrzf6a.fsf@gnu.org> (raw)
In-Reply-To: <87lipjr5jk.fsf_-_@lifelogs.com> (Ted Zlatanov's message of "Sat, 07 Jan 2012 08:44:15 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> I am seeing memory growth on GNU/Linux with Gnus and GnuTLS that I
> don't see otherwise without Gnus, so it's faintly possible GnuTLS is
> not the determining factor. I have gone over the gnutls.c code and
> don't see where the GnuTLS glue could be leaking.
Do you have a test case for, e.g. creating and closing a few thousand
GnuTLS connections to a localhost running apache with https and seeing
if there is any memory impact? That would be the first thing I would
try, but I haven't had the time to look into this.
next prev parent reply other threads:[~2012-01-07 15:49 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
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 ` Chong Yidong [this message]
2012-01-10 0:59 ` fixing memory leaks before the pretest 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=87sjjrzf6a.fsf@gnu.org \
--to=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).