https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70806
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2016-04-27
CC| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
No, there is no solution to dlclose of libstdc++ (or a lib statically linking
libstdc++/libsupc++) leaking that memory.
I can imagine that some configury could be added to make the allocation static
(the plan was to add a way to control the pool size via the environment which
is why it is now a dynamic allocation rather than a static one).
