Prev: Removing an EFI disk label
Next: Problem solved
From: Alan Coopersmith on 19 Jun 2008 15:03
Michael Vilain <vilain(a)NOspamcop.net> writes in comp.unix.solaris:
|Some time ago, Solaris' memory manager was changed so that memory that's
|been malloc'ed won't get free'ed until you actually quit the
|application.

Bullshit. Memory that is free'ed is returned to the application heap
for reuse by future malloc() calls, but not to the system until the
application exits. This is not a change made in Solaris, but the
original UNIX memory management design.

--
Alan Coopersmith * alanc(a)alum.calberkeley.org * Alan.Coopersmith(a)Sun.COM
http://blogs.sun.com/alanc/ * http://people.freedesktop.org/~alanc/
http://del.icio.us/alanc/ * http://www.csua.berkeley.edu/~alanc/
Working for, but definitely not speaking for, Sun Microsystems, Inc.
From: Andrew Gabriel on 19 Jun 2008 19:44
In article <vilain-7248D8.13304719062008(a)comcast.dca.giganews.com>,
Michael Vilain <vilain(a)NOspamcop.net> writes:
>
> But does the process' reported working set size decrease? Lots of
> newbie admins have posted here that they run a program and it's size in
> top keeps increasing. Then they ask if there's a memory leak.
>
> If free() returns the memory to the application stack, why isn't the
> working set updated? Or is the memory returned to the system-wide free
> list, which would make it available to the kernel or other processes.

Answered in my posting on 3rd June.

--
Andrew Gabriel
[email address is not usable -- followup in the newsgroup]
 | 
Pages: 1
Prev: Removing an EFI disk label
Next: Problem solved