From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Sven Joachim Newsgroups: gmane.emacs.devel Subject: Re: Emacs bzr memory footprint Date: Sat, 22 Oct 2011 10:44:31 +0200 Message-ID: <87wrbxza8g.fsf@turtle.gmx.de> 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> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1319273086 22340 80.91.229.12 (22 Oct 2011 08:44:46 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 22 Oct 2011 08:44:46 +0000 (UTC) Cc: Dmitry Antipov , Stefan Monnier , emacs-devel@gnu.org To: Carsten Mattner Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 22 10:44:42 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 1RHXC5-00021M-2v for ged-emacs-devel@m.gmane.org; Sat, 22 Oct 2011 10:44:41 +0200 Original-Received: from localhost ([::1]:52941 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RHXC4-0004P2-8J for ged-emacs-devel@m.gmane.org; Sat, 22 Oct 2011 04:44:40 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:35160) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RHXC0-0004ON-M6 for emacs-devel@gnu.org; Sat, 22 Oct 2011 04:44:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RHXBz-0005yq-F8 for emacs-devel@gnu.org; Sat, 22 Oct 2011 04:44:36 -0400 Original-Received: from mailout-de.gmx.net ([213.165.64.23]:45549) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RHXBz-0005yZ-0F for emacs-devel@gnu.org; Sat, 22 Oct 2011 04:44:35 -0400 Original-Received: (qmail invoked by alias); 22 Oct 2011 08:44:32 -0000 Original-Received: from p4FC7734A.dip.t-dialin.net (EHLO turtle.gmx.de) [79.199.115.74] by mail.gmx.net (mp061) with SMTP; 22 Oct 2011 10:44:32 +0200 X-Authenticated: #28250155 X-Provags-ID: V01U2FsdGVkX19kaPcYD6FkSH7q9b2FGuLdKrr8A7AY7s4u7c251D L5+X+wUVC6Es1l Original-Received: by turtle.gmx.de (Postfix, from userid 1000) id B94D03F504; Sat, 22 Oct 2011 10:44:31 +0200 (CEST) In-Reply-To: (Carsten Mattner's message of "Sat, 22 Oct 2011 09:34:35 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 213.165.64.23 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:145416 Archived-At: On 2011-10-22 09:34 +0200, Carsten Mattner wrote: > On Fri, Oct 21, 2011 at 8:00 PM, Stefan Monnier > wrote: >> > This creates two-level fragmentation: the whole heap is fragmented as seen >> > by malloc(), and allocated space is fragmented too, as seen by Emacs. Since >> >> Yes. >> >> > solid workload will consume 100M of the heap, the most of this 90M will be re-used - >> >> Exactly: so this fragmentation is not a serious problem in the sense >> that this free memory can be (re)used by Emacs. >> >> > but it will never freed. >> >> Right, so it's a problem in the sense that this memory will not be >> available to other processes. >> >> While this is not perfect, I don't consider it to be a serious problem. >> E.g. when people complain about Emacs using a lot of memory it's always >> (until now and I think in Nix's case as well) a case of too much memory >> being used because of something like a leak, and not just "Emacs doesn't >> return its free memory to the OS". > > It is a problem for everybody like me who doesn't have > gigs of free RAM. Sorry. > > I'll remember to --disable-gnutls and not use Gnus for my > own safety, for the moment. That's a good catch and seems > to help. Actually, Gnus is not a memory hog as long as you build Emacs "--without-gnutls". But with gnutls support, it's clearly leaking memory. Cheers, Sven