After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 89496 - GtkSocket does not disconnect toplevel_focus_in_handler after destoy
GtkSocket does not disconnect toplevel_focus_in_handler after destoy
Status: VERIFIED INCOMPLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
2.0.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2002-07-31 07:30 UTC by Robin Lu
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robin Lu 2002-07-31 07:30:21 UTC 
in gtksocket.c there's only gdk_window_add_filter but no
gdk_window_remove_filter. That cause gtk_socket_filter_func still works
even after my GtkSocket has been destroyed.
Comment 1 Robin Lu 2002-07-31 09:15:37 UTC 
I modified the summary. It seems only toplevel_focus_in_handler is not
disconnect correctly.
Comment 2 Owen Taylor 2002-07-31 18:31:34 UTC 
I need reproduction instructions here, and preferrably
a standalone test case. (mozilla isn't a useful test
case for me.) 

hierarchy_changed looks like it should properly remove the
handler to me.

Please reopen when you add more information.

(What version of GTK+? I assume 2.0.x for some x since
CVS head doesn't have toplevel_focus_in_handler)
Comment 3 Robin Lu 2002-08-01 03:25:35 UTC 
It's my fault. I didn't treat unparent correctly. Sorry for the confusion!