* Chet Ramey schrieb am 01.12.11 um 02:54 Uhr: > That's probably the result of the power-of-two allocation policy in the > bash malloc. When this came up before, I wrote: > > ========== > That's not a memory leak. Malloc implementations need not release > memory back to the kernel; the bash malloc (and others) do so only > under limited circumstances. Memory obtained from the kernel using > mmap or sbrk and kept in a cache by a malloc implementation doesn't > constitute a leak. A leak is memory for which there is no longer a > handle, by the application or by malloc itself. > ==========
Thanks for the explanation, Chat -Marc -- 8AAC 5F46 83B4 DB70 8317 3723 296C 6CCA 35A6 4134
