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: "pinskia 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 05:14:04 +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 #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to frankhb1989 from comment #7)
> This is definitely a leak from the view of libc. Why is the status INVALID
> instead of WONTFIX?
It is still reachable. Since it is reachable, a pointer at deconstructor time
could use it. This pool is used to low memory situations. And can be used
even near exit. There is no leak; a leak means it is no longer reachable.
Most programs will not free some of their memory at the end of their program
anyways; they would just call exit.