Comment 10 for bug 82123

I've had very little experience with manual memory management (my programming preferences tend to involve languages with automatic garbage collection), so I might be showing my ignorance here, but it seems to me that if you call malloc(), you should call free() when you're finished. If the memory footprint is growing--even if there's a peak somewhere--then some memory isn't getting freed, right? If that's the case, than it's a bug.