[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43389: 28.0.50; Emacs memory leaks
From: |
Eli Zaretskii |
Subject: |
bug#43389: 28.0.50; Emacs memory leaks |
Date: |
Tue, 17 Nov 2020 21:52:34 +0200 |
> From: DJ Delorie <dj@redhat.com>
> Cc: carlos@redhat.com, fweimer@redhat.com, 43389@debbugs.gnu.org
> Date: Tue, 17 Nov 2020 12:20:21 -0500
>
> Eli Zaretskii <eliz@gnu.org> 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.
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?
- bug#43389: 28.0.50; Emacs memory leaks, (continued)
- 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, 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 <=
- bug#43389: 28.0.50; Emacs memory leaks, DJ Delorie, 2020/11/17
- bug#43389: 28.0.50; Emacs memory leaks, Florian Weimer, 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, 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