From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#43389: 28.0.50; Emacs memory leaks using hard disk all time Date: Mon, 23 Nov 2020 19:39:35 +0000 Message-ID: References: <86y2j2brg2.fsf@protected.rcdrun.com> <83blfxth7c.fsf@gnu.org> <83y2j0qb2v.fsf@gnu.org> <831rgppg3w.fsf@gnu.org> <83zh3czbvz.fsf@gnu.org> <83blfovzxz.fsf@gnu.org> <83tutgufuf.fsf@gnu.org> <83lfervpvd.fsf@gnu.org> Reply-To: Andrea Corallo Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20336"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: fweimer@redhat.com, 43389@debbugs.gnu.org, bugs@gnu.support, dj@redhat.com, michael_heerdegen@web.de, trevor@trevorbentley.com, carlos@redhat.com, Arthur Miller To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Nov 23 20:41:21 2020 Return-path: Envelope-to: geb-bug-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 1khHiC-0005BI-Pq for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 23 Nov 2020 20:41:20 +0100 Original-Received: from localhost ([::1]:38652 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1khHiB-0000tW-Nq for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 23 Nov 2020 14:41:19 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55500) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1khHhu-0000rg-9s for bug-gnu-emacs@gnu.org; Mon, 23 Nov 2020 14:41:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39697) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1khHhu-00053m-2d for bug-gnu-emacs@gnu.org; Mon, 23 Nov 2020 14:41:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1khHht-0004AK-WF for bug-gnu-emacs@gnu.org; Mon, 23 Nov 2020 14:41:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Andrea Corallo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 23 Nov 2020 19:41:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 43389 X-GNU-PR-Package: emacs Original-Received: via spool by 43389-submit@debbugs.gnu.org id=B43389.160616041615948 (code B ref 43389); Mon, 23 Nov 2020 19:41:01 +0000 Original-Received: (at 43389) by debbugs.gnu.org; 23 Nov 2020 19:40:16 +0000 Original-Received: from localhost ([127.0.0.1]:51243 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1khHhA-00049A-AG for submit@debbugs.gnu.org; Mon, 23 Nov 2020 14:40:16 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:61612) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1khHh8-000492-KM for 43389@debbugs.gnu.org; Mon, 23 Nov 2020 14:40:14 -0500 Original-Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTP id 0ANJdaS8027756; Mon, 23 Nov 2020 19:39:36 GMT In-Reply-To: <83lfervpvd.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 23 Nov 2020 21:23:50 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:193960 Archived-At: I think would be nice to have a script that monitors Emacs memory footprint and attach gdb on it when the memory usage is over a certain (high) threshold. This way should be easy to see what we are doing because at that point we are supposed to be allocating extremely often. Andrea