From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Florian Weimer Newsgroups: gmane.emacs.devel Subject: Re: valgrind warnings [Re: Emacs bzr memory footprint] Date: Sun, 04 Dec 2011 22:11:47 +0100 Message-ID: <87y5us2ga4.fsf@mid.deneb.enyo.de> References: <87sjmvpmd2.fsf@lifelogs.com> <87aa93wmc4.fsf@turtle.gmx.de> <87sjmnrdjw.fsf@spindle.srvr.nix> <87ty73mc0m.fsf@spindle.srvr.nix> <4EA19111.7060401@yandex.ru> <87vcrhfmww.fsf@uwakimon.sk.tsukuba.ac.jp> <87pqhpf1qo.fsf@uwakimon.sk.tsukuba.ac.jp> <87k47qaxvz.fsf@lifelogs.com> <83bot1bovw.fsf@gnu.org> <87y5w531eo.fsf@uwakimon.sk.tsukuba.ac.jp> <83zkgla1mg.fsf@gnu.org> <87vcr92z6x.fsf@uwakimon.sk.tsukuba.ac.jp> <83ty6t9zd0.fsf@gnu.org> <878vo5xifo.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1323033123 24598 80.91.229.12 (4 Dec 2011 21:12:03 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 4 Dec 2011 21:12:03 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 04 22:11:59 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RXJLp-0004XX-CW for ged-emacs-devel@m.gmane.org; Sun, 04 Dec 2011 22:11:57 +0100 Original-Received: from localhost ([::1]:55237 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RXJLn-00028H-Vy for ged-emacs-devel@m.gmane.org; Sun, 04 Dec 2011 16:11:55 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:50996) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RXJLk-00027x-L2 for emacs-devel@gnu.org; Sun, 04 Dec 2011 16:11:53 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RXJLj-00086G-P3 for emacs-devel@gnu.org; Sun, 04 Dec 2011 16:11:52 -0500 Original-Received: from ka.mail.enyo.de ([87.106.162.201]:44396) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RXJLj-00085N-I9 for emacs-devel@gnu.org; Sun, 04 Dec 2011 16:11:51 -0500 Original-Received: from [172.17.135.4] (helo=deneb.enyo.de) by ka.mail.enyo.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) id 1RXJLf-0006iW-WE for emacs-devel@gnu.org; Sun, 04 Dec 2011 22:11:48 +0100 Original-Received: from fw by deneb.enyo.de with local (Exim 4.72) (envelope-from ) id 1RXJLf-0008Gp-OX for emacs-devel@gnu.org; Sun, 04 Dec 2011 22:11:47 +0100 In-Reply-To: <878vo5xifo.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 28 Oct 2011 11:08:27 -0400") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 87.106.162.201 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:146484 Archived-At: * Ted Zlatanov: > On Fri, 28 Oct 2011 07:52:12 -0400 Dan Nicolaescu wrote: > DN> On Fedora 15 with valgrind-3.6.1 it is possible to run > > DN> valgrind ./temacs > > I ran this and opened and closed a GnuTLS connection many times: > > (open-gnutls-stream "tls" "tls-buffer" "imap.gmail.com" "imaps") > > I did not see any errors printed when I did this, but on exit a lot of > information was printed that did not seem related (I could not analyze > it all, it was too much data and I don't know what to look for other > than "gnutls"). Is this enough to tell us there are no memory leaks in > the "open connection" part of the code? I'll test sending and receiving > data if so. I think you need to run valgrind --leak-check=yes ./temacs and actually terminate the program to get the dump of leaked resources. Has the bug been identified in the meantime? I've got some very long-running processes using GnuTLS which grow without bounds, too---but I've been blaming this on bugs in my Perl wrapper. In that cases, just opening and closing connections (and sending a bit of data) does not trigger the leak condition, either.