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: Memory again Date: Fri, 23 Dec 2011 13:41:40 +0900 Organization: Faculty of Science, Chiba University Message-ID: References: <71677AF5-0EE7-426E-B8FA-C2782B3CC36C@swipnet.se> <2AB13C59-F3BE-45F7-8C24-C88AA9AC8929@swipnet.se> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Trace: dough.gmane.org 1324615313 11198 80.91.229.12 (23 Dec 2011 04:41:53 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 23 Dec 2011 04:41:53 +0000 (UTC) Cc: emacs user , emacs-devel@gnu.org To: Jan =?ISO-8859-1?Q?Dj=E4rv?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 23 05:41:48 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 1Rdwx2-0000KQ-By for ged-emacs-devel@m.gmane.org; Fri, 23 Dec 2011 05:41:48 +0100 Original-Received: from localhost ([::1]:36824 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rdwx1-0001rH-Sg for ged-emacs-devel@m.gmane.org; Thu, 22 Dec 2011 23:41:47 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:45111) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rdwwy-0001r1-Oj for emacs-devel@gnu.org; Thu, 22 Dec 2011 23:41:45 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rdwwx-0001tX-I2 for emacs-devel@gnu.org; Thu, 22 Dec 2011 23:41:44 -0500 Original-Received: from mathmail.math.s.chiba-u.ac.jp ([133.82.132.2]:54135) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rdwwx-0001tB-8k for emacs-devel@gnu.org; Thu, 22 Dec 2011 23:41:43 -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 0EC59C055D; Fri, 23 Dec 2011 13:41:41 +0900 (JST) In-Reply-To: <2AB13C59-F3BE-45F7-8C24-C88AA9AC8929@swipnet.se> 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:146934 Archived-At: > Other than running valgrind on temacs, load everything in and then > print out reachable memory, I don't know how to check this. It > sounds as it isn't a leak as such, but something that is still > referenced, but not needed. The `heap' command might give some help. Perhaps one can compare results of `heaps -addresses all ' between before and after a VM invocation as explained in the manual page, and then use `malloc_history' to show the stack trace. YAMAMOTO Mitsuharu mituharu@math.s.chiba-u.ac.jp