From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Florian Weimer Newsgroups: gmane.emacs.bugs Subject: bug#43389: 28.0.50; Emacs memory leaks Date: Tue, 17 Nov 2020 21:13:00 +0100 Message-ID: <87a6vfkaib.fsf@oldenburg2.str.redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1418"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Cc: carlos@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 21:14:18 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 1kf7Mo-0000GV-EM for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 17 Nov 2020 21:14:18 +0100 Original-Received: from localhost ([::1]:49282 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kf7Mn-0006xC-H9 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 17 Nov 2020 15:14:17 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46726) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kf7MY-0006l6-RM for bug-gnu-emacs@gnu.org; Tue, 17 Nov 2020 15:14:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49704) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kf7MY-0003k6-Gs for bug-gnu-emacs@gnu.org; Tue, 17 Nov 2020 15:14:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kf7MY-0004zg-CF for bug-gnu-emacs@gnu.org; Tue, 17 Nov 2020 15:14:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Florian Weimer Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 17 Nov 2020 20:14: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.160564399219131 (code B ref 43389); Tue, 17 Nov 2020 20:14:02 +0000 Original-Received: (at 43389) by debbugs.gnu.org; 17 Nov 2020 20:13:12 +0000 Original-Received: from localhost ([127.0.0.1]:33017 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kf7Lj-0004yV-PM for submit@debbugs.gnu.org; Tue, 17 Nov 2020 15:13:12 -0500 Original-Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:57740) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kf7Li-0004yK-1X for 43389@debbugs.gnu.org; Tue, 17 Nov 2020 15:13:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1605643989; 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:references:references; bh=1VHw9HYKQtmcjEKx8Xxp7QnkIrjB45crPnp1eqXmmMs=; b=HE4jm46sXyKv+EOpHJvBIRm0yUM3UqyXZ/1GcY6t1qkxmPaqYcx7jUf/RXFeaHwZAXCBOB xa8hxGrTbqC9dQySv3yvhd6O88yHORO6Vj3OE08mcQjfsApQgvEFZs8VS4nlnDqPNAUF74 08yTDx5UxufP8xtIzndoKy0qgk/dinc= 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-36-7dqYd_PaPoCoest6RicEow-1; Tue, 17 Nov 2020 15:13:07 -0500 X-MC-Unique: 7dqYd_PaPoCoest6RicEow-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 7E0045F9DE; Tue, 17 Nov 2020 20:13:06 +0000 (UTC) Original-Received: from oldenburg2.str.redhat.com (ovpn-113-222.ams2.redhat.com [10.36.113.222]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6231F5D9CD; Tue, 17 Nov 2020 20:13:02 +0000 (UTC) In-Reply-To: (DJ Delorie's message of "Tue, 17 Nov 2020 14:59:54 -0500") X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=fweimer@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com 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:193573 Archived-At: * DJ Delorie: > Eli Zaretskii writes: >> 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? > > Well, both. The API allows you to start/stop tracing whenever you like, > but the state of your heap depends on the entire history of calls. > > So, for example, a trace during the "fast growth" period might show a > pattern that helps us[*] debug the problem, but if we want to > *reproduce* the problem, we'd need a full trace. > > [*] and by "us" I mostly mean "emacs developers who understand their > code" ;-) But how helpful would that be, given that malloc_info does not really show any inactive memory (discounting my 200 MiB hole)? We would need a comparable tracer for the Lisp-level allocator, I think. Thanks, Florian -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill