From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Memory again Date: Thu, 22 Dec 2011 19:39:15 -0500 Message-ID: References: <71677AF5-0EE7-426E-B8FA-C2782B3CC36C@swipnet.se> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1324600771 3739 80.91.229.12 (23 Dec 2011 00:39:31 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 23 Dec 2011 00:39:31 +0000 (UTC) Cc: Jan =?iso-8859-1?Q?Dj=E4rv?= , emacs-devel@gnu.org To: emacs user Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 23 01:39:27 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 1RdtAP-0002tY-6N for ged-emacs-devel@m.gmane.org; Fri, 23 Dec 2011 01:39:21 +0100 Original-Received: from localhost ([::1]:52534 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RdtAO-0003D0-HC for ged-emacs-devel@m.gmane.org; Thu, 22 Dec 2011 19:39:20 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:59624) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RdtAM-0003Cb-0H for emacs-devel@gnu.org; Thu, 22 Dec 2011 19:39:18 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RdtAL-0000J3-1J for emacs-devel@gnu.org; Thu, 22 Dec 2011 19:39:17 -0500 Original-Received: from smtp-02.vtx.ch ([194.38.175.91]:52908) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RdtAK-0000Iw-SP for emacs-devel@gnu.org; Thu, 22 Dec 2011 19:39:17 -0500 Original-Received: from ceviche.home (dyn.144-85-141-078.dsl.vtx.ch [144.85.141.78]) by smtp-02.vtx.ch (VTX Services SA) with ESMTP id ECF0E60674; Fri, 23 Dec 2011 01:39:15 +0100 (CET) Original-Received: by ceviche.home (Postfix, from userid 20848) id AD086660D5; Thu, 22 Dec 2011 19:39:15 -0500 (EST) In-Reply-To: (emacs user's message of "Thu, 22 Dec 2011 16:58:00 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-Received-From: 194.38.175.91 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:146930 Archived-At: >>> Thanks... =A0The leaks command indeed reports zero leaks now. =A0howeve= r, >>> emacs still grows every time I invoke vm. =A0here is a memory report >>> which I get after killing all buffers, when emacs is 214 Mb large (as >>> seen in the Activity Monitor). =A0 is this normal? >> As I'm not a vm-user I can't really say. =A0But it sounds like something= is >> not released back to the OS. > how does one go about diagnosing this? is it possible to tell if this > an elisp problem or a c-problem? The GC stats you posted indicate that the GC knows of about 27MB of data (10MB of which is actually unused but can't be returned to malloc due to fragmentation) which doesn't account for the 214MB you mention. So it looks like that data is held by the C code. Of course, I don't know what the 214MB represent, if it is resident set size, then there really seems to be a leak, whereas if it's the total virtual size, it may also be an artifact of various other things. Stefan