Bug#332182: I get a definite memory leak in GTK.

[polishedaussie at gmail.com]

Hi there.

This seemed very similar to my problem so I'll add my 2 cents to this bug.  
I actually HAVE a memory leak that is observable with top or ps. Valgrind  
spits out some errors (output attached) but they all seem to be as a  
result of the GTK libraries. The only bit of code that valgrind didn't  
like in my program was:

gtk_init (&argc, &argv);

Which is pretty hard to live without. I've included the program as an  
attachment (fgbgmodifier.c) if anyone would like to confirm the memory  
leak. To compile, use the command:

gcc -Wall -g fgbgmodifier.c -o fgbgmodifier `pkg-config --cflags --libs  
gtk+-2.0`

I've only seen it on my computer. I tested it on Ubuntu Hardy AMD64 (GTK  
version 2.12.9-3ubuntu2) on another computer and another person tested it  
on Solaris Express (GTK version 2.12.9.1209.9) and in both cases observed  
NO LEAK. I'm running libgtk2.0 version 2.12.11-3 on Debian unstable i386  
dist with AMD64 kernel.

I've also included the valgrind output (valgrind.log) for your perusal.  
I'm not experienced with it either so I can't give you any massive  
insights. For reference, the command I used to run valgrind was:

valgrind --tool=memcheck --leak-check=yes --show-reachable=yes  
--num-callers=20 --track-fds=yes --log-file=valgrind.log ./fgbgmodifier

If you think these bugs are not related, let me know and I'll submit a new  
one.

Adam
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fgbgmodifier.c
Type: application/octet-stream
Size: 1020 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20080907/1ae188c0/attachment-0002.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: valgrind.log
Type: application/octet-stream
Size: 196871 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20080907/1ae188c0/attachment-0003.obj