"...uses more memory over time..." Hmm, sounds like an actual leak to
me, unless there's some justification for it.
I agree that the problem is probably in someone's XS somewhere. But a
leak is a leak and is bad.
d
Perrin Harkins wrote:
On Wed, 2006-08-16 at 13:35 -0700, David Scott wrote:
Memory leak != memory hog. The leak could indicate instability and is a
much higher priority than "a measly couple of KB". Even little leaks
need to be plugged.
When people talk about "memory leaks" on this list, they almost never
mean actual leaks. What they mean is "uses more memory over time." A
leak would mean that some memory is allocated and then lost in the
cracks, i.e. some kind of pointer bug or something at the C level. Perl
and apache have been cleaned of these pretty well by now.
One place where people do find actual leaks sometimes is in modules that
use XS code. Fixing that kind of leak can be hard and certainly
requires some serious C chops.
- Perrin
