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 516776 - make closure disconnection for connect_object safe for unref() in another thread
make closure disconnection for connect_object safe for unref() in another thread
Status: RESOLVED DUPLICATE of bug 667145
Product: glib
Classification: Platform
Component: gobject
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Tim Janik
gtkdev
Depends on:
Blocks:
 
 
Reported: 2008-02-16 00:28 UTC by Allison Karlitskaya (desrt)
Modified: 2012-01-19 03:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Allison Karlitskaya (desrt) 2008-02-16 00:28:38 UTC
19:25 < tjafk2> desrt: now i understand what you're after. you want the 
                connect_object disconnect handler to be thread-safe. good 
                point, file a gnome bug about, should be worth fixing.

essentially, you should be able to call g_object_unref() on an object in one thread while a signal is being dispatched with that object as the argument in another thread.

either:

1) the signal should dispatch (with the signal handling code taking a reference)

or

2) nothing should happen (the closure is disabled before anything happens)

but never 

3) *boom*
Comment 1 Allison Karlitskaya (desrt) 2012-01-19 03:38:00 UTC
oops

*** This bug has been marked as a duplicate of bug 667145 ***