From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Madhu Newsgroups: gmane.emacs.help Subject: Re: memory leaks Date: Mon, 14 Sep 2020 15:36:57 +0530 Message-ID: References: <835zlntmjk.fsf@gnu.org> <8336grtjak.fsf@gnu.org> <83zh5vcdx5.fsf@gnu.org> <878sde6c5i.fsf@gmail.com> <83imcidcfp.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12029"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Mon Sep 14 12:28:18 2020 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kHlib-0002wT-99 for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 14 Sep 2020 12:28:17 +0200 Original-Received: from localhost ([::1]:39654 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kHlia-00077I-A9 for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 14 Sep 2020 06:28:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35344) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kHlhy-0006oe-Da for help-gnu-emacs@gnu.org; Mon, 14 Sep 2020 06:27:38 -0400 Original-Received: from [59.96.48.198] (port=50160 helo=localhost.localdomain) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kHlhw-0000qs-2R for help-gnu-emacs@gnu.org; Mon, 14 Sep 2020 06:27:38 -0400 Original-Received: (qmail 14414 invoked by uid 500); 14 Sep 2020 10:06:57 -0000 In-Reply-To: (Stefan Monnier's message of "Sun, 13 Sep 2020 16:14:36 -0400") X-Host-Lookup-Failed: Reverse DNS lookup failed for 59.96.48.198 (failed) Received-SPF: softfail client-ip=59.96.48.198; envelope-from=enometh@meer.net; helo=localhost.localdomain X-detected-operating-system: by eggs.gnu.org: First seen = 2020/09/14 06:06:32 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x (no timestamps) [generic] [fuzzy] X-Spam_score_int: 29 X-Spam_score: 2.9 X-Spam_bar: ++ X-Spam_report: (2.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_PBL=3.335, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:124047 Archived-At: * Stefan Monnier : Wrote on Sun, 13 Sep 2020 16:14:36 -0400: > The `garbage-collect` command actually can return info about the current > Lisp heap use. The `memory-usage` package can display it in a more > user-friendly format. > > That can be very useful to see if those 500MB belong to the Lisp heap or > to ... something else (typically libraries, like those of the GUI or > those used to display images). The numbers I reported by garbage-collect do not account for the memory usage. FWIW I've posted that info again at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43395 In 2019 i suspected the culprit was the fonts system. It doesn't seem to be toolkit related. I don't use emacs as an imageviewer (but I have to check that). Since the interest in CONFIG_PSI there are a number of tools on github that monitor memory - it should be possible to come up with some tool that alerts emacs of memory surges while keeping some history.