This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/66339] g++ 5.1.0 Generates memory leak
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 19 Sep 2016 11:31:00 +0000
- Subject: [Bug libstdc++/66339] g++ 5.1.0 Generates memory leak
- Auto-submitted: auto-generated
- References: <bug-66339-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
--- Comment #13 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note the pool was made dynamic (and effectively larger) exactly for a QOI
issue...
[the dynamic nature is to make its size controllable by the environment, sth
that didn't materialize yet]
The difficulty with freeing is that it is necessary until the dynamic loader
can get rid of the C++ runtime. There isn't a way to enforce releasing at that
point
(apart from making it static storage).