Re: [gtk-list] Re: how can I trust glib when it has so many mem leaks?

[Ionutz Borcoman <borco borco-ei eng hokudai ac jp>]

Havoc Pennington wrote:
> 
> They aren't really leaks in glib, glib just keeps chunks of memory around
> and recycles them. This makes it run a lot faster. The memory is never
> released to the operating system, just back to glib. So you should just
> ignore everything ccmalloc and friends report for glib.

This is INSANE ! It's like giving a kid a posisoned candy :-(
How can I differentiate what ccmalloc sais for glib comparred with what
it says for my program ?
I have try to statically link my program in the hope that that memory
will be released when glib unloads. Never. The garbage is still there.
Is glib recovering memory from one instance to another ? How ?

I don't need reasurances that glib has no memory leaks. I whant a way to
check my program. Maybe I'll believe you that glib has no memory leaks,
but this is not helping me in debuging my stuff.

I would be much more happy if glib will report to me that XXX memory has
been kept for recycling and to see that that XXX. Also, when a program
is started, to report that YYY memory has been recovered. And a simple
algorithm, like a function f(garbage, XXX, YYY) that make me sure I
don't have memory leaks. This should be done for cases when I compile
glib with debug enabled.

TIA,

Ionutz