Dispatch dbus messages after method calls when no main loop running
authorMike Gorse <mgorse@linux-sh69.site>
Wed, 21 Aug 2013 19:33:18 +0000 (14:33 -0500)
committerMike Gorse <mgorse@linux-sh69.site>
Wed, 21 Aug 2013 19:33:18 +0000 (14:33 -0500)
commitec424c4b688f002af44dd052f4a29feb3868921d
tree44d99f0b5a001ec9bda1478220250c4d3a96d195
parent94106405aad216434789e3a4c4a76c1f47a65959
Dispatch dbus messages after method calls when no main loop running

If no main loop is running, then the dbus connection's incoming message
queue was never emptied, so with, eg, dogtail,
dbus_connection_send_with_reply_and_block would take longer and longer
to look through the message queue to find a reply. This also effectively
led to a memory leak.

https://bugzilla.gnome.org/show_bug.cgi?id=701145
atspi/atspi-misc.c
dbind/dbind.c