https://bugs.kde.org/show_bug.cgi?id=448991
Tom Hughes <t...@compton.nu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |NOT A BUG
CC| |t...@compton.nu
--- Comment #1 from Tom Hughes <t...@compton.nu> ---
That's not a leak - as valgrind says that memory is still reachable. A leak is
memory is unreachable because there are no pointers to it but it hasn't been
freed.
What you're looking at is some sort of cache inside the dynamic linker.
Possibly it's a glibc bug, in that we deliberately call __libc_freeres to ask
glibc to free it's internal resources at exit (which doesn't happen normally)
but it's not a valgrind bug.
--
You are receiving this mail because:
You are watching all bug changes.
