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 754730 - GDBusConnection::closed vs g_dbus_connection_is_closed()
GDBusConnection::closed vs g_dbus_connection_is_closed()
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gdbus
unspecified
Other Linux
: Normal normal
: ---
Assigned To: David Zeuthen (not reading bugmail)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2015-09-08 15:19 UTC by Dan Winship
Modified: 2018-05-24 18:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dan Winship 2015-09-08 15:19:58 UTC
When GDBusConnection::closed is emitted in the remote_peer_disconnected case, FLAG_CLOSED gets set on the connection, but it does not get fully cleaned up. In particular, if the connection is a private bus connection, the local socket remains open, and gets leaked when the connection is destroyed.

g_dbus_connection_close() will clean things up correctly in this case, but g_dbus_connection_close_sync() won't, because it checks for FLAG_CLOSED and does nothing in that case.
Comment 1 GNOME Infrastructure Team 2018-05-24 18:13:24 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/1080.