Commit ed6c1423 authored by GMT 2001  Tony Gale's avatar GMT 2001 Tony Gale Committed by Tony Gale

New question re memory leaks.

Tue Feb 27 13:37:38 GMT 2001  Tony Gale <gale@gtk.org>

        * docs/faq/gtk-faq.sgml: New question re memory leaks.
parent 5c28d2ca
Tue Feb 27 13:37:38 GMT 2001 Tony Gale <gale@gtk.org>
* docs/faq/gtk-faq.sgml: New question re memory leaks.
2001-02-25 Hans Breuer <hans@breuer.org>
* gdk/gdk.h : changed #ifdef GDK_DISBALE_DEPRECARED to #ifndef
......
Tue Feb 27 13:37:38 GMT 2001 Tony Gale <gale@gtk.org>
* docs/faq/gtk-faq.sgml: New question re memory leaks.
2001-02-25 Hans Breuer <hans@breuer.org>
* gdk/gdk.h : changed #ifdef GDK_DISBALE_DEPRECARED to #ifndef
......
Tue Feb 27 13:37:38 GMT 2001 Tony Gale <gale@gtk.org>
* docs/faq/gtk-faq.sgml: New question re memory leaks.
2001-02-25 Hans Breuer <hans@breuer.org>
* gdk/gdk.h : changed #ifdef GDK_DISBALE_DEPRECARED to #ifndef
......
Tue Feb 27 13:37:38 GMT 2001 Tony Gale <gale@gtk.org>
* docs/faq/gtk-faq.sgml: New question re memory leaks.
2001-02-25 Hans Breuer <hans@breuer.org>
* gdk/gdk.h : changed #ifdef GDK_DISBALE_DEPRECARED to #ifndef
......
Tue Feb 27 13:37:38 GMT 2001 Tony Gale <gale@gtk.org>
* docs/faq/gtk-faq.sgml: New question re memory leaks.
2001-02-25 Hans Breuer <hans@breuer.org>
* gdk/gdk.h : changed #ifdef GDK_DISBALE_DEPRECARED to #ifndef
......
Tue Feb 27 13:37:38 GMT 2001 Tony Gale <gale@gtk.org>
* docs/faq/gtk-faq.sgml: New question re memory leaks.
2001-02-25 Hans Breuer <hans@breuer.org>
* gdk/gdk.h : changed #ifdef GDK_DISBALE_DEPRECARED to #ifndef
......
Tue Feb 27 13:37:38 GMT 2001 Tony Gale <gale@gtk.org>
* docs/faq/gtk-faq.sgml: New question re memory leaks.
2001-02-25 Hans Breuer <hans@breuer.org>
* gdk/gdk.h : changed #ifdef GDK_DISBALE_DEPRECARED to #ifndef
......
......@@ -2283,6 +2283,25 @@ distribution, in the file <filename>gtk/testdnd.c</filename>.</para>
</sect1>
<!-- ----------------------------------------------------------------- -->
<sect1>
<title>Why does GTK+/GLib leak memory?</title>
<para>It doesn't. Both GLib and the C library (malloc implementation)
will cache allocated memory on occasion, even if you free it with
free().</para>
<para>So you can't generally use tools such as top to see if you are
using free() properly (aside from the very roughest of estimations, i.e.
if you are really, really screwing up top will show that, but you can't
distinguish small mistakes from the GLib/malloc caches).</para>
<para>In order to find memory leaks, use proper memory profiling
tools.</para>
</sect1>
</chapter>
<!-- ***************************************************************** -->
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment