From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Memory usage report Date: Fri, 18 Sep 2020 16:17:04 +0300 Message-ID: <83o8m34433.fsf@gnu.org> References: <87lfh8kyot.fsf@gnus.org> <83k0ws5hzt.fsf@gnu.org> <87h7rwkxtk.fsf@gnus.org> <83imcb61p7.fsf@gnu.org> <871rizl5mf.fsf@gnus.org> <83r1qz48h3.fsf@gnu.org> <871rizjogr.fsf@gnus.org> <83pn6j45rr.fsf@gnu.org> <87wo0ri6kz.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1567"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 18 15:22:24 2020 Return-path: Envelope-to: ged-emacs-devel@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 1kJGLI-0000JS-Ck for ged-emacs-devel@m.gmane-mx.org; Fri, 18 Sep 2020 15:22:24 +0200 Original-Received: from localhost ([::1]:42488 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kJGLH-0002cQ-DV for ged-emacs-devel@m.gmane-mx.org; Fri, 18 Sep 2020 09:22:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43014) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kJGFx-0005b0-1j for emacs-devel@gnu.org; Fri, 18 Sep 2020 09:16:56 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46792) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kJGFw-0000tG-OJ; Fri, 18 Sep 2020 09:16:52 -0400 Original-Received: from [176.228.60.248] (port=3452 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kJGFw-0001OD-2A; Fri, 18 Sep 2020 09:16:52 -0400 In-Reply-To: <87wo0ri6kz.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 18 Sep 2020 14:59:24 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:256083 Archived-At: > From: Lars Ingebrigtsen > Cc: emacs-devel@gnu.org > Date: Fri, 18 Sep 2020 14:59:24 +0200 > > Eli Zaretskii writes: > > >> That can have significant memory? > > > > Some of them could, yes. > > Do you know which ones? bidi_cache, for one. > > Why would an image cache take that much? we flush it from time to > > time, and I have difficulty believing that all those users reporting > > large memory footprints load thousands of images every hour of every > > day. > > It is unlikely that "all those users" use that many images, but some > may. (As you no doubt remember, calling `image-size' in a loop will > kill Emacs with an out of memory fault.) That loop is highly unlikely to happen in practice, certainly not happen constantly in a long-lived session. > >> > Which variables did you have in mind in this context? Can you show an > >> > example? > >> > >> It'd just traverse all the variables and compute the "largest" ones. > > > > Again, they are included in the GC report. So what do you expect to > > see? > > I expect to see what variables take "all that size"? I'm not sure what > you're asking here. I guess I don't understand the utility of knowing, e.g., which Lisp string in the current session is the longest one. What would you do with such information? > > So, while a more detailed report might be nice to have, I don't see > > how it would help to diagnose "leaks" of the kind we are discussing > > now on the bug list. > > I am not talking about any bug report in particular. If I were, that is > where I would have posted this. Then I guess I don't understand the purpose of the features you'd like to have. Can you explain?