From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: Emacs bzr memory footprint Date: Thu, 27 Oct 2011 18:10:56 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87k47qaxvz.fsf@lifelogs.com> References: <83fwix2osa.fsf@gnu.org> <0B3EE7A4-D0D6-4D1E-ADC4-0BEE68F179B2@mit.edu> <87fwivwp37.fsf@turtle.gmx.de> <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> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1319753478 18214 80.91.229.12 (27 Oct 2011 22:11:18 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 27 Oct 2011 22:11:18 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 28 00:11:15 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 1RJYAM-0003nF-RZ for ged-emacs-devel@m.gmane.org; Fri, 28 Oct 2011 00:11:15 +0200 Original-Received: from localhost ([::1]:58364 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RJYAM-0002G4-9E for ged-emacs-devel@m.gmane.org; Thu, 27 Oct 2011 18:11:14 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:47238) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RJYAJ-00027M-6c for emacs-devel@gnu.org; Thu, 27 Oct 2011 18:11:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RJYAH-0005B7-Ig for emacs-devel@gnu.org; Thu, 27 Oct 2011 18:11:11 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:46291) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RJYAH-0005B2-6x for emacs-devel@gnu.org; Thu, 27 Oct 2011 18:11:09 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RJYAG-0003iI-7K for emacs-devel@gnu.org; Fri, 28 Oct 2011 00:11:08 +0200 Original-Received: from c-76-28-40-19.hsd1.vt.comcast.net ([76.28.40.19]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Oct 2011 00:11:08 +0200 Original-Received: from tzz by c-76-28-40-19.hsd1.vt.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Oct 2011 00:11:08 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 22 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: c-76-28-40-19.hsd1.vt.comcast.net X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.90 (gnu/linux) Cancel-Lock: sha1:NEjHWQhC/nv0gNwf4WXJzLQkqjY= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 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:145684 Archived-At: On Sun, 23 Oct 2011 01:08:15 +0900 "Stephen J. Turnbull" wrote: SJT> Carsten Mattner writes: >> Is the gnutls memory usage a leak, or just some allocated arrays for >> crypto arrays? Just a wild guess, nothing scientific to back it up. SJT> It sounds like a leak to me, since the reports we're seeing are of SJT> memory creeping up over time. I would expect any arrays to be on the SJT> order of a few MB, not 100s. We have 3 reports from Sven Joachim, Nix, and Carsten Mattner. I will do my best to find the issues. They seem to be in the C code I wrote to link with GnuTLS. It would be really helpful if someone who knows C debugging well could run Valgrind or something similar against Emacs with GnuTLS compiled, hitting all these leaks. I will take a look at the code, since I am also reviewing it to prevent the lockups on hung connections, but concrete Valgrind reports would be great. Thanks Ted