David Zeuthen c4081f9abd GDBusConnection: Avoid callbacks on finalized connection
Turns out that GDBusWorker will issue callbacks (in its own thread)
even after g_dbus_worker_stop() has been called. This would rarely
happen (and unreffing a connection is even rarer) so only saw this bug
occasionally when running the gdbus-connection test case in a loop.

Fix up this issue by maintaining a set of GDBusConnection objects that
are currently "alive" and do nothing in the callbacks if the passed
user_data pointer is not in this set.

Also attempted to fix up a race condition with
_g_object_wait_for_single_ref_do() and its use of GObject toggle
references - for now, just resort to busy waiting, thereby
sidestepping the toggle reference mess altogether.

Signed-off-by: David Zeuthen <davidz@redhat.com>
2010-09-24 14:48:33 -04:00
..
2010-07-05 00:56:12 -04:00
2010-07-30 19:51:20 -04:00
2010-07-05 03:09:36 -04:00
2010-09-03 16:00:15 -04:00
2010-04-17 01:48:05 -04:00
2010-06-09 10:32:36 +02:00
2010-09-03 15:56:23 -04:00
2010-05-10 08:07:28 -04:00
2010-08-06 13:05:18 -04:00
2010-07-09 07:24:08 -04:00
2010-04-17 01:48:05 -04:00
2010-09-03 15:44:28 -04:00
2010-08-03 10:41:21 -04:00