GNU bug report logs - #43389
28.0.50; Emacs memory leaks

Previous Next

Package: emacs;

Reported by: Michael Heerdegen <michael_heerdegen <at> web.de>

Date: Mon, 14 Sep 2020 00:44:01 UTC

Severity: normal

Merged with 43395, 43876, 44666

Found in version 28.0.50

Done: Stefan Monnier <monnier <at> iro.umontreal.ca>

Bug is archived. No further changes may be made.

Full log

Message #179 received at 43389 <at> debbugs.gnu.org (full text, mbox):

From: DJ Delorie <dj <at> redhat.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: carlos <at> redhat.com, fweimer <at> redhat.com, 43389 <at> debbugs.gnu.org
Subject: Re: bug#43389: 28.0.50; Emacs memory leaks
Date: Tue, 17 Nov 2020 14:59:54 -0500

Eli Zaretskii <eliz <at> gnu.org> 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" ;-)
This bug report was last modified 4 years and 57 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.