Re: Help with GtkBuilder memory leak

[Giovanni Panozzo <giovanni panozzo it>]

> Yes, various libraries in the stack perform one-off allocations; these
> are *NOT* leaks, since they do not grow unbounded and are collected by
> the OS at the end of the process.

Yes!

I modified builderleak.c allocating 1000 times GtkBuilder and 
deallocating it just after. The leak reported by the address sanitizer 
is exactly big as the one with a single GtkBuilder allocation
(8681 bytes in 308 allocations)

So you are right, it's a "one time" allocation meant to be freed by the 
OS. It seems to be only a problem with libfontconfing: all other 
libraries I use, do not expose this behavior.

> When using Valgrind, you can also use suppression files which can
> remove false positives and help you pinpoint the actual leaks in your
> code.

With ASAN can be done too... I will blacklist them in some way.

Thank you

Ciao
Giovanni