From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/31103] New: periodically malloc_trim()
Date: Thu, 30 Nov 2023 20:58:27 +0000 [thread overview]
Message-ID: <bug-31103-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
Bug ID: 31103
Summary: periodically malloc_trim()
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: fche at redhat dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
debuginfod's memory usage can fluctuate widely during the scan & groom phases.
In the same places where we call sqlite3_db_release_memory() - and maybe more
of the same - we should subsequently call malloc_trim().
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-11-30 20:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 20:58 fche at redhat dot com [this message]
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
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@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).