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 14:59:54 -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="24690"; 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 21:01:39 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 1kf7AZ-0006LG-6L for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 17 Nov 2020 21:01:39 +0100 Original-Received: from localhost ([::1]:43312 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kf7AY-0003R0-64 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 17 Nov 2020 15:01:38 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43928) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kf79y-00031p-86 for bug-gnu-emacs@gnu.org; Tue, 17 Nov 2020 15:01:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49694) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kf79x-0007Z8-U3 for bug-gnu-emacs@gnu.org; Tue, 17 Nov 2020 15:01:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kf79x-0004hX-Rh for bug-gnu-emacs@gnu.org; Tue, 17 Nov 2020 15: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 20: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.160564321017999 (code B ref 43389); Tue, 17 Nov 2020 20:01:01 +0000 Original-Received: (at 43389) by debbugs.gnu.org; 17 Nov 2020 20:00:10 +0000 Original-Received: from localhost ([127.0.0.1]:33007 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kf798-0004gF-9w for submit@debbugs.gnu.org; Tue, 17 Nov 2020 15:00:10 -0500 Original-Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:49701) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kf794-0004f2-Ic for 43389@debbugs.gnu.org; Tue, 17 Nov 2020 15:00:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1605643206; 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=esHczOjRPpa2OzL1v48AoQqnpmRi3gGAF0ZMIxdLsiQ=; b=D8rebv08AzaPiYbOZ1WeeJB1fWh5IC5G1ZlTxo23XGtWj9HQ7D/SdkivWHNMXNpqwswyQi A7t165dwKk8Yxv1RUvBHtiaYOITchMy1gXGfm41lo89kgI8OTY0F1zw4jNU+2GHLzQD2ui ftNEkrmeoVj8EFwRE3/2aEg38hqhL20= 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-297-pHvgr3ZfPsq_f3pPV0jDHw-1; Tue, 17 Nov 2020 15:00:04 -0500 X-MC-Unique: pHvgr3ZfPsq_f3pPV0jDHw-1 Original-Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 2D75564147; Tue, 17 Nov 2020 20:00:03 +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 B9D9C5C1CF; Tue, 17 Nov 2020 19:59:55 +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 0AHJxsW4002842; Tue, 17 Nov 2020 14:59:54 -0500 In-Reply-To: <83h7pnrcal.fsf@gnu.org> (message from Eli Zaretskii on Tue, 17 Nov 2020 21:52:34 +0200) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 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-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:193571 Archived-At: 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" ;-)