Re: Memory leaks

[Bill C <czermak netspace net au>]

On 10/02/11 04:01, James Morris wrote:
> On 9 February 2011 16:10, Michael Cronenworth<mike cchtml com>  wrote:
> That's called patronising. I have been there already. What good is a
> work in progress when the progress stopped over two years ago?
>
> Not only do we have to write our own code, we have to put work into
> making other peoples code ignore the errors in other peoples code so
> we can see the errors in our own code. It's a bloody outrage!
> _______________________________________________
> gtk-app-devel-list mailing list
> gtk-app-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
My experience with valgrind and GTK is that it is easy to fix leaks.

Simply look for leaked memory that you allocated.  Then determine where 
you should have released it.  If it was not allocated by you its not 
your problem so ignore it.

Works for me, but I rely on minimal third party software and compile 
everything with debug enabled.  Dont see any sign of leakage problems in 
GTK, but I dont claim to use all its features; only the ones I need for 
my GUI code.

From time to time I use valgrind to check for leaks with GTK2+ programs 
written in C and it is clear that there are  no leaks.  Have not tried 
GTK3.  Have not tried the C++ wrappers.

Dont use an IDE.  Maybe the problems you have are outside GTK.

Rgds Bill C