From: Ronny Meeus <ronny.meeus@gmail.com>
To: libc-help@sourceware.org
Cc: Ronny Meeus <ronny.meeus@gmail.com>
Subject: Memory increase using glibc - 2.35
Date: Tue, 7 Feb 2023 09:21:18 +0100 [thread overview]
Message-ID: <CAMJ=MEeVTuPGVa6K-C9KEU=u4vSv9N401ro4a7=hZ6=Zy=L-xA@mail.gmail.com> (raw)
Hello
we recently did an upstep to glibc-2.35 (from glibc-2.34) and we
observed a substantial memory increase in 1 application.
Our embedded SW is running on Linux 4.1.52 on ARM CPUs and consists of
many applications.
All apps, except 1, are consuming more or less the same amount of memory.
Note that these apps are executing a malloc_trim periodically (no clue
whether that has something to do with it).
For the problematic application (which is not executing malloc_trim),
the memory consumption increased from 250Mb to 300Mb, with the same
configuration.
We did already a "pmap" of the both apps and the observation is that
there are a lot more (and bigger in size) anon pages allocated when
running 2.35.
The complete increase of 50Mb can be traced back to the increase of these pages.
Can this be explained by one of the changes in 2.35?
We are not using any tuneables.
Thanks.
Best regards,
Ronny
next reply other threads:[~2023-02-07 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 8:21 Ronny Meeus [this message]
2023-02-21 14:52 ` Szabolcs Nagy
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMJ=MEeVTuPGVa6K-C9KEU=u4vSv9N401ro4a7=hZ6=Zy=L-xA@mail.gmail.com' \
--to=ronny.meeus@gmail.com \
--cc=libc-help@sourceware.org \
/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.
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).