[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43389: 28.0.50; Emacs memory leaks
From: |
Florian Weimer |
Subject: |
bug#43389: 28.0.50; Emacs memory leaks |
Date: |
Tue, 17 Nov 2020 21:13:00 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
* DJ Delorie:
> Eli Zaretskii <eliz@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" ;-)
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
- bug#43389: 28.0.50; Emacs memory leaks, (continued)
- bug#43389: 28.0.50; Emacs memory leaks, Jean Louis, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, DJ Delorie, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, Jean Louis, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/11/18
- bug#43389: 28.0.50; Emacs memory leaks, Jean Louis, 2020/11/23
- bug#43389: 28.0.50; Emacs memory leaks, Carlos O'Donell, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, DJ Delorie, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, DJ Delorie, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks,
Florian Weimer <=
- bug#43389: 28.0.50; Emacs memory leaks, DJ Delorie, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, Florian Weimer, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, Florian Weimer, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, Carlos O'Donell, 2020/11/18
- bug#43389: 28.0.50; Emacs memory leaks, Jean Louis, 2020/11/18
- bug#43389: 28.0.50; Emacs memory leaks, Andreas Schwab, 2020/11/18
- bug#43389: 28.0.50; Emacs memory leaks, Jean Louis, 2020/11/18