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: Sat, 19 Sep 2020 17:48:46 +0300 Message-ID: <83eemx3jqp.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> <83o8m34433.fsf@gnu.org> <87imcb43e3.fsf@localhost> <83k0wr4222.fsf@gnu.org> <87zh5nfa95.fsf@gnus.org> <87mu1ndsez.fsf@gnus.org> <83d02j3x9t.fsf@gnu.org> <87eemxrgdz.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31505"; mail-complaints-to="usenet@ciao.gmane.io" Cc: yantar92@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 19 16:49:23 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 1kJeAz-000841-T2 for ged-emacs-devel@m.gmane-mx.org; Sat, 19 Sep 2020 16:49:21 +0200 Original-Received: from localhost ([::1]:54246 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kJeAz-0006uj-0J for ged-emacs-devel@m.gmane-mx.org; Sat, 19 Sep 2020 10:49:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37566) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kJeAU-0006VM-R6 for emacs-devel@gnu.org; Sat, 19 Sep 2020 10:48:50 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:45727) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kJeAU-0005TH-F8; Sat, 19 Sep 2020 10:48:50 -0400 Original-Received: from [176.228.60.248] (port=3190 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kJeAT-0001gN-Ow; Sat, 19 Sep 2020 10:48:50 -0400 In-Reply-To: <87eemxrgdz.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 19 Sep 2020 16:27:20 +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:256177 Archived-At: > From: Lars Ingebrigtsen > Date: Sat, 19 Sep 2020 16:27:20 +0200 > Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, yantar92@gmail.com > > > But in all of the cases where people complained about such huge RSS, > > the GC report shows a very small Lisp memory usage, so that helm cache > > cannot be the culprit. It's something else, whether related to > > helm-ff-keep-cached-candidates or some other feature. > > I just gave you an example of the opposite, and then you say "in all of > the cases"? I'm not sure what you are arguing here, or even why you are > arguing about this: Giving users a convenient way to examine (and rule > out) certain memory usage problems surely can't be bad in itself. We are talking about two different use cases, I think: I was talking about the problems described in bug#43389. I have no objections to producing more detailed memory usage reports based on Lisp data. I'm just saying that I usually find that not very helpful for investigating problems like the bug mentioned above. I'm sorry I annoyed you.