https://bugs.kde.org/show_bug.cgi?id=371471
Tom Hughes <t...@compton.nu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Tom Hughes <t...@compton.nu> ---
So this is the leak it is reporting:
==24123== 72,704 bytes in 1 blocks are still reachable in loss record 1 of 1
==24123== at 0x62228BAD: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==24123== by 0x624C0A5F: ??? (in /usr/lib64/libstdc++.so.6.0.22)
==24123== by 0x6160CD89: call_init.part.0 (in /usr/lib64/ld-2.23.so)
==24123== by 0x6160CE9A: _dl_init (in /usr/lib64/ld-2.23.so)
==24123== by 0x615FDCB9: ??? (in /usr/lib64/ld-2.23.so)
So it's nothing to do with the placement new but rather is some initialisation
inside the standard library. It's also still reachable when the program
terminates, so not really a leak at all, which is why the details aren't shown
by default.
In the newly released 3.12.0 it goes away anyway because we now call the
libstdc++ cleanup routine at exit by default.
--
You are receiving this mail because:
You are watching all bug changes.
