Re: [GtkGLExt] 20 byte memory leak

[Mukund Sivaraman <muks banu com>]

On Sun, Oct 03, 2010 at 03:08:10PM +0300, Mihai Draghicioiu wrote:
> ==10164== 20 bytes in 1 blocks are still reachable in loss record 1 of 1
> ==10164==    at 0x402328F: calloc (vg_replace_malloc.c:467)
> ==10164==    by 0x5F5D105: _dlerror_run (dlerror.c:142)
> ==10164==    by 0x5F5CB40: dlopen@@GLIBC_2.1 (dlopen.c:88)
> ==10164==    by 0x4277C08: ??? (in /usr/lib/libGL.so.195.36.24)

This was probably created by some loaded shared object, that was since
dlclose()d or such.  That's how you get the ???s in Valgrind.  Because
this seems to be an NVIDIA driver going by that libGL.so.195.36.24
filename, it could also be self-modifying code.  I don't know.

This has nothing to do with GtkGLExt libraries. You can get the same
stacktrace by compiling your code as:

echo "int main() {}" > g.c && \
gcc g.c `pkg-config pangox --libs` -lGL -og

It might be something with the Pango X library. Use of that library is
going away in any case.

> Call me anal, but i'd like to reduce memory leaks to zero in my
> application. Is there a way of removing this 20 byte leak? I realize

This pursuit is a waste of time, and you should not ask on this list in
any case.  Memory leaks that developers take seriously are the ones
that grow over time, not static allocations that stick around.  If you
are that pedantic, you are bound to see memory in use when you quit a
GTK+ app after calling gtk_init().  It's something that the kernel
takes care of very well.

		Mukund