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.

diff --git a/ChangeLog b/ChangeLog
index cfd87a593adc57d0c23a4a2e79c0401da63def92..a613f1cde15cf42d72475972b68a3de6227fb89b 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+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

diff --git a/ChangeLog.pre-2-0 b/ChangeLog.pre-2-0
index cfd87a593adc57d0c23a4a2e79c0401da63def92..a613f1cde15cf42d72475972b68a3de6227fb89b 100644 (file)
--- a/ChangeLog.pre-2-0
+++ b/ChangeLog.pre-2-0
@@ -1,3 +1,7 @@
+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

diff --git a/ChangeLog.pre-2-10 b/ChangeLog.pre-2-10
index cfd87a593adc57d0c23a4a2e79c0401da63def92..a613f1cde15cf42d72475972b68a3de6227fb89b 100644 (file)
--- a/ChangeLog.pre-2-10
+++ b/ChangeLog.pre-2-10
@@ -1,3 +1,7 @@
+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

diff --git a/ChangeLog.pre-2-2 b/ChangeLog.pre-2-2
index cfd87a593adc57d0c23a4a2e79c0401da63def92..a613f1cde15cf42d72475972b68a3de6227fb89b 100644 (file)
--- a/ChangeLog.pre-2-2
+++ b/ChangeLog.pre-2-2
@@ -1,3 +1,7 @@
+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

diff --git a/ChangeLog.pre-2-4 b/ChangeLog.pre-2-4
index cfd87a593adc57d0c23a4a2e79c0401da63def92..a613f1cde15cf42d72475972b68a3de6227fb89b 100644 (file)
--- a/ChangeLog.pre-2-4
+++ b/ChangeLog.pre-2-4
@@ -1,3 +1,7 @@
+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

diff --git a/ChangeLog.pre-2-6 b/ChangeLog.pre-2-6
index cfd87a593adc57d0c23a4a2e79c0401da63def92..a613f1cde15cf42d72475972b68a3de6227fb89b 100644 (file)
--- a/ChangeLog.pre-2-6
+++ b/ChangeLog.pre-2-6
@@ -1,3 +1,7 @@
+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

diff --git a/ChangeLog.pre-2-8 b/ChangeLog.pre-2-8
index cfd87a593adc57d0c23a4a2e79c0401da63def92..a613f1cde15cf42d72475972b68a3de6227fb89b 100644 (file)
--- a/ChangeLog.pre-2-8
+++ b/ChangeLog.pre-2-8
@@ -1,3 +1,7 @@
+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

diff --git a/docs/faq/gtk-faq.sgml b/docs/faq/gtk-faq.sgml
index e986e4512c4fea7125baa1d29f7f5b8510a19712..1f9f9b2c41bb708193322d49f5d55506364f219b 100644 (file)
--- a/docs/faq/gtk-faq.sgml
+++ b/docs/faq/gtk-faq.sgml
@@ -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>
 
 <!-- ***************************************************************** -->