> This is, methinks, a libc problem...malloc() will (when necessary) aquire
> a heap of memory w/ a system call, then allocate segments within that
> heap; free() marks those sections of the heap "de-allocated", but does not
> return it to the OS until the program exits.
Doesnt the "new" malloc in libc 5.3.12 returns memory to the OS when
free is called?