[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#38345: 27.0.50; Permanent increase in memory consumption after openi
From: |
Eli Zaretskii |
Subject: |
bug#38345: 27.0.50; Permanent increase in memory consumption after opening images (or pdfs) |
Date: |
Sat, 07 Dec 2019 21:39:35 +0200 |
> From: Noam Postavsky <npostavs@gmail.com>
> Cc: yantar92@gmail.com, 38345@debbugs.gnu.org, juri@linkov.net
> Date: Sat, 07 Dec 2019 14:25:06 -0500
>
> > So does this mean modern glibc has no knobs to tailor its behavior to
> > various needs, like set the threshold for using mmap, etc.? IOW, no
> > more support for the likes of mallopt?
>
> Looks like mallopt is still there, but Emacs' DOUG_LEA_MALLOC code
> depends on malloc_set_state and malloc_get_state which were removed in
> glibc 2.25 (2017).
> https://sourceware.org/ml/libc-alpha/2017-02/msg00079.html
Thanks. Then I don't understand why our calls to mallopt are
conditioned on DOUG_LEA_MALLOC. What they are supposed to do should
be good for modern glibc versions as well.