IIRC, the libc will not return any deallocated memory directly to the
system, but it will return them to a pool of available memory instead.
This way it doesn't need to get new pages from the system every time
you need them, but this means also that the memory footprint of your
program will never really decrease during its run... on linux (and all
good unix, BTW) this is not an issue, since the very same libc marks
these freed pages as swappable, as well as unused, so if linux really
needs, they can be removed and/or destroyed.
plus, it seems that even the glib library uses this approach... as far
as I can tell...
--
Stud. Marco Pietrobono | Murphy's Law: if something could
v. del Calice, 39 - 00178 ROMA | go wrong, it does.
Tel. +39.6.7186329 0339.7410893 | Legge di Murphy: se qualcosa può
http://www.pietrobo.com | andar male, lo farà.
------------------------------------------------------------------------
Some men see things as they are and say, why;
I dream things that never were and say, why not. ( George Bernard Shaw )
+---------------------------------------------------------------------+
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the line "unsubscribe glade-devel" in the body of the message.
