From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: yantar92@gmail.com, 38345@debbugs.gnu.org, juri@linkov.net
Subject: bug#38345: 27.0.50; Permanent increase in memory consumption after opening images (or pdfs)
Date: Fri, 06 Dec 2019 09:52:38 +0200 [thread overview]
Message-ID: <83immthovt.fsf@gnu.org> (raw)
In-Reply-To: <87r21ick48.fsf@gmail.com> (message from Noam Postavsky on Thu, 05 Dec 2019 20:34:31 -0500)
> From: Noam Postavsky <npostavs@gmail.com>
> Cc: Ihor Radchenko <yantar92@gmail.com>, 38345@debbugs.gnu.org, juri@linkov.net
> Date: Thu, 05 Dec 2019 20:34:31 -0500
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > No. AFAIK, any compilation on GNU/Linus defines DOUG_LEA_MALLOC.
>
> That's not the case with modern glibc, hence all that trouble with
> ralloc, etc during Emacs 25.
I was judging by what I see on fencepost.gnu.org, but I guess that
isn't "modern" anymore.
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? If so, perhaps the reports
about jemalloc's superior performance should be sent to glibc
developers, as they could have a proper advice for that.
next prev parent reply other threads:[~2019-12-06 7:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 14:37 bug#38345: 27.0.50; Permanent increase in memory consumption after opening images (or pdfs) Ihor Radchenko
[not found] ` <handler.38345.B.15745199896049.ack@debbugs.gnu.org>
2019-11-23 14:44 ` bug#38345: Acknowledgement (27.0.50; Permanent increase in memory consumption after opening images (or pdfs)) Ihor Radchenko
2019-11-23 14:48 ` bug#38345: 27.0.50; Permanent increase in memory consumption after opening images (or pdfs) Lars Ingebrigtsen
2019-11-23 15:12 ` Ihor Radchenko
2019-11-23 14:50 ` Eli Zaretskii
2019-11-23 15:18 ` Ihor Radchenko
2019-11-23 15:45 ` Eli Zaretskii
2019-11-23 16:04 ` Ihor Radchenko
2019-11-23 16:34 ` Eli Zaretskii
2019-11-23 17:33 ` Ihor Radchenko
2019-11-23 17:51 ` Eli Zaretskii
2019-11-25 16:10 ` Eli Zaretskii
2019-11-26 15:21 ` Ihor Radchenko
2019-11-26 15:55 ` Eli Zaretskii
2019-11-26 16:24 ` Ihor Radchenko
2019-11-27 21:17 ` Juri Linkov
2019-11-28 1:38 ` Ihor Radchenko
2019-11-28 12:35 ` Lars Ingebrigtsen
2019-11-28 13:11 ` Ihor Radchenko
2019-11-28 15:10 ` Eli Zaretskii
2019-11-28 17:27 ` Ihor Radchenko
2019-11-28 18:44 ` Eli Zaretskii
2019-12-02 8:04 ` Ihor Radchenko
2019-12-02 15:49 ` Eli Zaretskii
2019-12-05 6:48 ` Ihor Radchenko
2019-12-05 14:52 ` Eli Zaretskii
2019-12-06 1:34 ` Noam Postavsky
2019-12-06 7:52 ` Eli Zaretskii [this message]
2019-12-07 19:25 ` Noam Postavsky
2019-12-07 19:39 ` Eli Zaretskii
2019-12-16 6:18 ` Ihor Radchenko
2019-12-16 16:30 ` Eli Zaretskii
2020-08-02 18:14 ` Lars Ingebrigtsen
2020-08-02 22:52 ` Ihor Radchenko
2020-08-03 6:10 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83immthovt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38345@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=npostavs@gmail.com \
--cc=yantar92@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).