https://bugs.kde.org/show_bug.cgi?id=426751
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=426751
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=426751
--- Comment #5 from Paul Floyd ---
I think the glib memory was due to some other library (I was also trying to
debug https://bugs.kde.org/show_bug.cgi?id=472409)
Will probably close this soon.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=426751
--- Comment #4 from Paul Floyd ---
hello world in C++ for me has 8 still reachable
6 small ones in glib
1 16k in glib
1 72k in libstdc++
glib is rather stinky when it comes to cleaning up memory
the libstdc++ memory should be freed via the
https://bugs.kde.org/show_bug.cgi?id=426751
--- Comment #3 from Paul Floyd ---
Never did get round to checking. I'm not sure that it is libc allocating the
memory - could be libstc++ as well.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426751
Sam James changed:
What|Removed |Added
CC||s...@gentoo.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=426751
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=426751
ledrag...@free.fr changed:
What|Removed |Added
CC||ledrag...@free.fr
--- Comment #1 from
