From: "dichen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/31103] periodically malloc_trim()
Date: Fri, 15 Mar 2024 01:54:02 +0000 [thread overview]
Message-ID: <bug-31103-10460-40EEZHqVLC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31103-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
--- Comment #8 from Di Chen <dichen at redhat dot com> ---
Got it. I have used GDB to make debuginfod stop at
1) before malloc_trim(0)
$ cat /proc/$$/statm
228487 3456 2976 48 0 19049 0
2) after malloc_trim(0)
$ cat /proc/$$/statm
228462 3456 2976 48 0 19024 0
debuginfod's VmSize and VmData did shrink some.
$ cat /proc/$$/status
Name: debuginfod
...
VmSize: 913948 kB -> 913848 kB
VmData: 76060 kB -> 75960 kB
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-15 1:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 20:58 [Bug debuginfod/31103] New: " fche at redhat dot com
2024-01-31 23:19 ` [Bug debuginfod/31103] " dichen at redhat dot com
2024-03-01 11:49 ` dichen at redhat dot com
2024-03-01 13:25 ` fche at redhat dot com
2024-03-02 20:58 ` mark at klomp dot org
2024-03-12 11:43 ` dichen at redhat dot com
2024-03-12 12:39 ` fche at redhat dot com
2024-03-14 3:42 ` dichen at redhat dot com
2024-03-14 13:22 ` fche at redhat dot com
2024-03-15 1:54 ` dichen at redhat dot com [this message]
2024-03-15 12:29 ` fche at redhat dot com
2024-03-18 1:35 ` dichen at redhat dot com
2024-03-19 11:06 ` fche at redhat dot com
2024-03-19 12:14 ` dichen at redhat dot com
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=bug-31103-10460-40EEZHqVLC@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).