From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: How safe is it to change vanilla-USE-Flag in glibc?
Date: Wed, 6 Jul 2016 15:06:20 +0000 (UTC) [thread overview]
Message-ID: <loom.20160706T170123-43@post.gmane.org> (raw)
In-Reply-To: 1.467.789.450-ner-566@TP_L520
Franz Fellner <alpine.art.de <at> gmail.com> writes:
> I have issues with some prgrams eating too much memory. This seems to be
related to glibc not trimming as
> necessary which results in way too much memory still occupied by the
program after free()ing memory.
Perhaps you should file a bug, providing some evidence if other distros are
affected (this suggests it might be a gcc issue) or other distros are not
affected (this suggests it might be a gentoo pathch issue)?
> Franz
hth,
James
next prev parent reply other threads:[~2016-07-06 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 7:17 [gentoo-user] How safe is it to change vanilla-USE-Flag in glibc? Franz Fellner
2016-07-06 15:06 ` James [this message]
2016-07-06 17:10 ` [gentoo-user] " Franz Fellner
2016-07-06 18:46 ` Fernando Rodriguez
2016-07-06 15:19 ` [gentoo-user] " Michael Orlitzky
2016-07-06 17:02 ` Franz Fellner
2016-07-06 17:11 ` Michael Orlitzky
2016-07-06 17:16 ` Michael Orlitzky
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=loom.20160706T170123-43@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.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