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.bugs Subject: bug#43389: 28.0.50; Emacs memory leaks Date: Tue, 17 Nov 2020 21:52:34 +0200 Message-ID: <83h7pnrcal.fsf@gnu.org> References: Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34685"; mail-complaints-to="usenet@ciao.gmane.io" Cc: carlos@redhat.com, fweimer@redhat.com, 43389@debbugs.gnu.org To: DJ Delorie Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Nov 17 20:54:36 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 1kf73j-0008uM-Pj for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 17 Nov 2020 20:54:35 +0100 Original-Received: from localhost ([::1]:38420 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kf73i-0000uk-Sd for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 17 Nov 2020 14:54:34 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42482) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kf72E-0008Ah-Mp for bug-gnu-emacs@gnu.org; Tue, 17 Nov 2020 14:53:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49690) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kf72E-0004Z1-Cr for bug-gnu-emacs@gnu.org; Tue, 17 Nov 2020 14:53:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kf72E-0004Uu-Bv for bug-gnu-emacs@gnu.org; Tue, 17 Nov 2020 14:53:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 17 Nov 2020 19:53:02 +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.160564276717267 (code B ref 43389); Tue, 17 Nov 2020 19:53:02 +0000 Original-Received: (at 43389) by debbugs.gnu.org; 17 Nov 2020 19:52:47 +0000 Original-Received: from localhost ([127.0.0.1]:33003 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kf71z-0004UR-G1 for submit@debbugs.gnu.org; Tue, 17 Nov 2020 14:52:47 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:42292) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kf71x-0004UE-27 for 43389@debbugs.gnu.org; Tue, 17 Nov 2020 14:52:46 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:33300) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kf71r-0004Qx-JZ; Tue, 17 Nov 2020 14:52:39 -0500 Original-Received: from [176.228.60.248] (port=1124 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kf71q-0000ur-4j; Tue, 17 Nov 2020 14:52:39 -0500 In-Reply-To: (message from DJ Delorie on Tue, 17 Nov 2020 12:20:21 -0500) 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:193570 Archived-At: > From: DJ Delorie > Cc: carlos@redhat.com, fweimer@redhat.com, 43389@debbugs.gnu.org > Date: Tue, 17 Nov 2020 12:20:21 -0500 > > Eli Zaretskii writes: > > You mean, trace all the memory allocations in Emacs with the tracer? > > That would produce huge amounts of data, as Emacs calls malloc at an > > insane frequency. Or maybe I don't understand what kind of tracing > > procedure you had in mind > > That's exactly what it does, and yes, it easily generates gigabytes > (sometimes terabytes) of trace information. But it also captures the > most accurate view of what's going on, and lets us replay (via > simulation) all the malloc API calls, so we can reproduce most > malloc-related problems on a whim. Is it possible to start tracing only when the fast growth of memory footprint commences? Or is tracing from the very beginning a necessity for providing meaningful data?