From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: DJ Delorie Newsgroups: gmane.emacs.bugs Subject: bug#43389: 28.0.50; Emacs memory leaks Date: Tue, 17 Nov 2020 12:20:21 -0500 Message-ID: References: <87r1r5428d.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31495"; mail-complaints-to="usenet@ciao.gmane.io" Cc: carlos@redhat.com, fweimer@redhat.com, 43389@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Nov 17 20:01:10 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 1kf6E2-00085n-H5 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 17 Nov 2020 20:01:10 +0100 Original-Received: from localhost ([::1]:56792 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kf6E0-00049Y-VF for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 17 Nov 2020 14:01:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58664) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kf6Du-00049N-5y for bug-gnu-emacs@gnu.org; Tue, 17 Nov 2020 14:01:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49622) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kf6Dt-0003Ft-Qb for bug-gnu-emacs@gnu.org; Tue, 17 Nov 2020 14:01:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kf6Dt-0003Em-O9 for bug-gnu-emacs@gnu.org; Tue, 17 Nov 2020 14:01:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: DJ Delorie Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 17 Nov 2020 19:01: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.160563965612424 (code B ref 43389); Tue, 17 Nov 2020 19:01:01 +0000 Original-Received: (at 43389) by debbugs.gnu.org; 17 Nov 2020 19:00:56 +0000 Original-Received: from localhost ([127.0.0.1]:32935 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kf6Dk-0003EH-Qn for submit@debbugs.gnu.org; Tue, 17 Nov 2020 14:00:56 -0500 Original-Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:48862) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kf4f9-0000lb-7n for 43389@debbugs.gnu.org; Tue, 17 Nov 2020 12:21:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1605633631; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=K9A7xYtqLUMK923n8ubKHRyBsPl6JniUA7s9j5cD+Hk=; b=ffh8LKIpetMDqGVTthbJHjZE//V4H+nb6ASwaibOq1Sifg8xL60Qj33jt+B2Ky4zcEZg5n j4jSJE85ilUjJTcgoxo5Kf8Y7zBXLxxJUt3PJfuTtJp2rd43heR6DeyyXikgGKh9zb12Er ipFY0HnwNCfljT5VDgyVyg4ZC8LBwlY= Original-Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-401-dNmY_1TsOYinDYuM0h7kCA-1; Tue, 17 Nov 2020 12:20:29 -0500 X-MC-Unique: dNmY_1TsOYinDYuM0h7kCA-1 Original-Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 2A1D0804017; Tue, 17 Nov 2020 17:20:27 +0000 (UTC) Original-Received: from greed.delorie.com (ovpn-112-249.rdu2.redhat.com [10.10.112.249]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 93E575D9CC; Tue, 17 Nov 2020 17:20:23 +0000 (UTC) Original-Received: from greed.delorie.com.redhat.com (localhost [127.0.0.1]) by greed.delorie.com (8.14.7/8.14.7) with ESMTP id 0AHHKLFD032477; Tue, 17 Nov 2020 12:20:22 -0500 In-Reply-To: <83mtzfrjod.fsf@gnu.org> (message from Eli Zaretskii on Tue, 17 Nov 2020 19:13:06 +0200) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dj@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com X-Mailman-Approved-At: Tue, 17 Nov 2020 14:00:51 -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:193568 Archived-At: 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.