[procps] Re: bug #627257, top: memory leaks
- From: Jim Warner <james.warner@xxxxxxxxxxx>
- To: procps@xxxxxxxxxxxxx
- Date: Mon, 12 Mar 2012 11:04:20 -0500
On Mar 12, 2012, at 6:23 AM, Craig Small wrote:
On Fri, Mar 09, 2012 at 11:15:32AM -0600, Jim Warner wrote:
>> Here's a little more information on the above bug.
> Thanks for the analysis, mind if i forward it to the bug system?
> Yes, it seems a minor thing and I'm not surprised its lurking in
> libproc.
Craig,
Don't mind at all -- it's already public.
But thanks for asking...
Jim
Note for libproc1 ----------------------------- :
We should strive to track all such (pwcache) library acquired dynamic memory in
some sort of library interface struct (PROCTAB maybe?).
That way, an iterative program like top could chose to avoid the valgrind
"definitely lost" warning by calling some library cleanup function or freeing
stuff itself.
(I see no reason to try and avoid the "possibly lost" warnings)
Other related posts:
