[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 91153] Possible new leak to suppress in glibc-2.?.supp
From:       Tom Hughes <thh () cyberscience ! com>
Date:       2004-10-31 22:15:29
Message-ID: 20041031221529.17923.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
        
http://bugs.kde.org/show_bug.cgi?id=91153        




------- Additional Comments From thh cyberscience com  2004-10-31 23:15 -------
It isn't really a case of anything being to blame - the real point here is that there \
isn't really a problem. Memory that is still in use when the program exits is not a \
problem as such which is why valgrind doesn't report reachable memory as a leak \
unless you ask for it with --show-reachable=yes.

If you call pthread_exit rather than exit then the TSD destructors will be run and \
that memory will be freed. But if the program is exiting anyway then why do you care \
if the memory is explicitly freed or not?


[prev in list] [next in list] [prev in thread] [next in thread]