https://bugs.kde.org/show_bug.cgi?id=448991
Yahya Jaafar <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Yahya Jaafar <[email protected]> --- (In reply to Alex from comment #2) > (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... Hi, can you please tell me what they said to you? -- You are receiving this mail because: You are watching all bug changes.
