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 459555 - gdk_threads_add_* docs question
gdk_threads_add_* docs question
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Backend: X11
unspecified
Other Linux
: Normal minor
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2007-07-23 13:36 UTC by Christian Persch
Modified: 2015-05-10 20:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Persch 2007-07-23 13:36:37 UTC 
The docs of gdk_threads_add_*_full don't state whether the gdk lock is also held during the invocation of the provided GDestroyNotify function. From reading the code I see that they don't; so that should be documented to make it clear that you need to do that yourself if necessary.
Comment 1 Tim Janik 2007-08-22 09:47:07 UTC 
unfortunately the glib main loop mechanism allows sources to be destroyed during dispatching (e.g. when a timeout/idler is removed while the gdk lock is being held) and also after all GSources have been dispatched (e.g. due to a reference count which was held across dispatch()). so whether the gdk lock is being held during destroy is unpredictable.
Comment 2 Tim Janik 2007-08-24 13:22:11 UTC 
Discussion started on a possible remedy here: http://mail.gnome.org/archives/gtk-devel-list/2007-August/msg00081.html
Comment 3 Matthias Clasen 2015-05-10 20:00:40 UTC 
no activity in a long time here.