From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ihor Radchenko <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: Sun, 02 Aug 2020 20:14:29 +0200 [thread overview]
Message-ID: <87k0yggbju.fsf@gnus.org> (raw)
In-Reply-To: <83y2vc44j4.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 16 Dec 2019 18:30:07 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> However, looking at the C code, I don't understand then why the
>> memory consumption is increasing. I can only see that too many images in
>> c->images array can cause extra memory consumption, which cannot cause
>> the observed memory leak.
>
> I guess that's because the freed memory is not at the end of the heap,
> and this cannot be returned to the OS.
This was half a year ago, and skimming this bug report, it seems like
this was the tentative conclusion -- there's no memory leak, just the
allocator not returning the memory back to the OS.
If that's the case, then this bug report can be closed?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-02 18:14 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
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 [this message]
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=87k0yggbju.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=38345@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--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).