The free(3) libc function rarely returns memory back to the system. Most
commonly, memory freed using free(3) is retained by the application for
use by subsequent calls to malloc and friends. There are some
implementations of malloc/free that do return memory back to the OS,
but only in some very pristine cases. (TRU64 actually does this).
On 23 Jul 2000, at 9:48, Benjamin Scott wrote:
> Not gonna happen. Programs call free() when they're done using a block of
> memory; not before, and not after. Actually, in Netscape's case, it often
> doesn't call free() even after it's done using the memory. :-( You might
> find a program that will call internal garbage collection routines when a
> malloc() fails, but if Netscape was that smart, the ulimit fix would have
> worked.
>
> The problem is Netscape's memory management is horrid. To paraphrase a
> certain kernel developer, it should be shown to small children when they've
> been especially bad. :-) The only solution is to fix Netscape. Hopefully
> Mozilla will do that.
--
Jerry Feldman
Contractor, eInfrastructure Partner Engineering
508-467-4315 http://www.testdrive.compaq.com/linux/
Compaq Computer Corp.
200 Forest Street MRO1-3/F1
Marlboro, Ma. 01752
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
