[Bug 37078] crashes if connecting fails just before it succeeds
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue May 10 20:14:22 CEST 2011
https://bugs.freedesktop.org/show_bug.cgi?id=37078
--- Comment #1 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2011-05-10 11:14:21 PDT ---
Created an attachment (id=46559)
View: https://bugs.freedesktop.org/attachment.cgi?id=46559
Review: https://bugs.freedesktop.org/review?bug=37078&attachment=46559
set_status_to_connected: do nothing if we already disconnected
Now that we're making more use of GAsyncResult, we can easily get into
this situation:
* all but one of the preconditions for being CONNECTED have happened;
the remaining one uses GAsyncResult (currently that can only be
conn_presence_set_initial_presence_async)
* conn_presence_set_initial_presence succeeds, and schedules a call
to its callback in an idle; we are now ready to be CONNECTED, but because
of GAsyncResult calling conventions, we won't call the callback right now
* someone calls Disconnect(), and we do so, synchronously; we are now
DISCONNECTED
* the idle goes off and connection_initial_presence_cb is called,
with success, while DISCONNECTED!
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the telepathy-bugs
mailing list