Re: free() and memory usage
From: those who know me have no need of my name (not-a-real-address_at_usa.net)
Date: 02/29/04
- Next message: those who know me have no need of my name: "Re: popen()"
- Previous message: Jo: "Timeout for connect()"
- In reply to: concern: "free() and memory usage"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 29 Feb 2004 00:07:20 GMT
in comp.unix.programmer i read:
>1) the size of top constantly grows means a leak?
not necessarily.
>2) if free() of glibc doesn't (always?) return the memory to OS, is this
>behave can be affected by process' current running env or time(how long the
>process holds the resource) related?
gnu libc only returns memory to the o/s when there is a sufficiently large
block. see the documentation for more information.
>3) what are other possible reasons for above different "size" with same
>inputs/outputs to a process?
something is different it would seem. find those differences.
-- a signature
- Next message: those who know me have no need of my name: "Re: popen()"
- Previous message: Jo: "Timeout for connect()"
- In reply to: concern: "free() and memory usage"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|