From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: YAMAMOTO Mitsuharu Newsgroups: gmane.emacs.devel Subject: Re: fixing memory leaks before the pretest (was: Update on the Emacs release schedule?) Date: Sun, 08 Jan 2012 11:39:27 +0900 Organization: Faculty of Science, Chiba University Message-ID: References: <87vcookmxd.fsf@gnu.org> <87lipjr5jk.fsf_-_@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1325990386 25481 80.91.229.12 (8 Jan 2012 02:39:46 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 8 Jan 2012 02:39:46 +0000 (UTC) Cc: emacs-devel@gnu.org To: Carsten Mattner Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 08 03:39:41 2012 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 1Rjifd-0001ti-E0 for ged-emacs-devel@m.gmane.org; Sun, 08 Jan 2012 03:39:41 +0100 Original-Received: from localhost ([::1]:42116 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rjifb-0003D8-OB for ged-emacs-devel@m.gmane.org; Sat, 07 Jan 2012 21:39:39 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:48371) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RjifY-0003D3-US for emacs-devel@gnu.org; Sat, 07 Jan 2012 21:39:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RjifW-0005dd-RO for emacs-devel@gnu.org; Sat, 07 Jan 2012 21:39:36 -0500 Original-Received: from mathmail.math.s.chiba-u.ac.jp ([133.82.132.2]:62700) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RjifW-0005d8-71 for emacs-devel@gnu.org; Sat, 07 Jan 2012 21:39:34 -0500 Original-Received: from church.math.s.chiba-u.ac.jp (church [133.82.132.36]) by mathmail.math.s.chiba-u.ac.jp (Postfix) with ESMTP id E2C33C055D; Sun, 8 Jan 2012 11:39:27 +0900 (JST) In-Reply-To: User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.3 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI) X-detected-operating-system: by eggs.gnu.org: NetBSD 3.0 (DF) X-Received-From: 133.82.132.2 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:147470 Archived-At: >>>>> On Sat, 7 Jan 2012 17:57:38 +0100, Carsten Mattner said: > 2012/1/7 Ted Zlatanov : >> On Sat, 07 Jan 2012 15:10:38 +0800 Chong Yidong >> wrote: >>=20 CY> As for the code, there are still a number of issues that need more CY> attention, most prominently the mysterious memory leak(s) that may CY> or may not involve Gnus and/or GnuTLS and/or Mac OS X. >>=20 >> 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. =A0I have gone over the gnutls.c code >> and don't see where the GnuTLS glue could be leaking. =A0If it is, >> I'll need a tool like Valgrind to help me, and last time I tried >> that, the reports were not helpful to me (too much data, not enough >> leading back to GnuTLS). =A0I spent 2 days on this last week and >> meant to bring it up this week, actually (the discussion about >> GnuTLS on W32 sort of distracted me :) >>=20 >> Maybe someone who actually knows how to use Valgrind could help me >> or try to find the leaks themselves? > Tried LLVM AddressSanitizer? It's supposed to be a low-impact > compile flag. http://clang.llvm.org/docs/AddressSanitizer.html > From the documentation I'm not sure it's useful for finding leaks. I suggested a possible way to analyze heap usage on Mac OS X only using some commands that bundled with the standard developer tools: http://lists.gnu.org/archive/html/emacs-devel/2011-12/msg00552.html . Has anybody who are seeing memory issues on Mac OS X tried this? At least we can make sure whether there are some bogus root references or freed memory is not returned to the system. YAMAMOTO Mitsuharu mituharu@math.s.chiba-u.ac.jp