[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: |
Fri, 18 Sep 2020 09:56:14 +0300 |
> Date: Thu, 17 Sep 2020 17:58:51 -0400
> From: Joshua Branson via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
>
> Over in #guix irc, the guix people seemed to think it was a memory leak with
> helm.
Thanks.
But if it's due to helm, why doesn't the huge memory usage show in the
report produced by GC? That report should show all the Lisp object
that we allocate and manage, no? Where does helm-ff-cache keeps those
"candidates"? (And what is this cache, if someone could be kind
enough to describe it?)
- bug#43389: 28.0.50; Emacs memory leaks, Michael Heerdegen, 2020/09/13
- bug#43389: 28.0.50; Emacs memory leaks, Juri Linkov, 2020/09/14
- bug#43389: 28.0.50; Emacs memory leaks, Michael Heerdegen, 2020/09/14
- bug#43389: 28.0.50; Emacs memory leaks, Russell Adams, 2020/09/15
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/09/15
- bug#43389: 28.0.50; Emacs memory leaks, Russell Adams, 2020/09/15
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/09/16
- bug#43389: 28.0.50; Emacs memory leaks, Russell Adams, 2020/09/17
- bug#43389: 28.0.50; Emacs memory leaks, Joshua Branson, 2020/09/17
- bug#43389: 28.0.50; Emacs memory leaks, Russell Adams, 2020/09/17
- bug#43389: 28.0.50; Emacs memory leaks,
Eli Zaretskii <=
- bug#43389: 28.0.50; Emacs memory leaks, Robert Pluim, 2020/09/18
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/09/18
- bug#43389: 28.0.50; Emacs memory leaks, jbranso, 2020/09/20
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/09/18
bug#43389: 28.0.50; Emacs memory leaks, Thomas Ingram, 2020/09/17