[valgrind] [Bug 448991] leak on fedora 33 and higher in getaddrinfo

[Tom Hughes]

https://bugs.kde.org/show_bug.cgi?id=448991

Tom Hughes  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG
 CC||t...@compton.nu

--- Comment #1 from Tom Hughes  ---
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.

[valgrind] [Bug 448991] leak on fedora 33 and higher in getaddrinfo

[Alex]

https://bugs.kde.org/show_bug.cgi?id=448991

--- Comment #2 from Alex  ---
(In reply to Tom Hughes from comment #1)
> 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.

Thanks I'll try to open a bug with glibc...

-- 
You are receiving this mail because:
You are watching all bug changes.