luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-02-04 10:16:17 +01:00
Code Issues Packages Projects Releases Wiki Activity

Document the fact that g_signal_connect_object() does *not* remove the

Browse Source 
Sun Mar 14 11:00:41 2004  Owen Taylor  <otaylor@redhat.com>

        * gobject/tmpl/signals.sgml: Document the fact that
        g_signal_connect_object() does *not* remove the signal
        when the object is disconnected currently and describe
        a workaround to prevent memory leaks.
This commit is contained in:
Owen Taylor 2004-03-14 16:34:23 +00:00 committed by Owen Taylor
parent 2f11709f3b
commit 8e4b5453a7
2 changed files with 30 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/reference/ChangeLog
View File

@ -1,3 +1,10 @@
Sun Mar 14 11:00:41 2004 Owen Taylor <otaylor@redhat.com>
* gobject/tmpl/signals.sgml: Document the fact that
g_signal_connect_object() does *not* remove the signal
when the object is disconnected currently and describe
a workaround to prevent memory leaks.
Tue Mar 9 09:16:11 2004 Owen Taylor <otaylor@redhat.com>
* === Released 2.3.6 ===

24
docs/reference/gobject/tmpl/signals.sgml
View File

@ -490,7 +490,29 @@ calling the handler.
<!-- ##### FUNCTION g_signal_connect_object ##### -->
<para>
This is similar to g_signal_connect_data(), but uses a closure which
ensures that the object stays alive during the call to @c_handler.
ensures that the @gobject stays alive during the call to @c_handler
by temporarily adding a reference count to @gobject.
</para>
<para>
Note that there this a bug in GObject that makes this function
much less useful than it might seem otherwise. Once @gobject is
disposed, the callback will no longer be called, but, the signal
handler is <emphasis>not</emphasis> currently disconnected. If the
@instance is itself being freed at the same time than this doesn't
matter, since the signal will automatically be removed, but
if @instance persists, then the signal handler will leak. You
should not remove the signal yourself because in a future versions of
GObject, the handler <emphasis>will</emphasis> automatically
be disconnected.
</para>
<para>
It's possible to work around this problem in a way that will
continue to work with future versions of GObject by checking
that the signal handler is still connected before disconnected it:
<informalexample><programlisting>
if (g_signal_handler_is_connected (instance, id))
g_signal_handler_disconnect (instance, id);
</informalexample></example>
</para>
@instance: the instance to connect to.