| commit | 70c36aed6de4660015cd952e0e11a3e9d05005f4 | |
| author | Stefan Becker <chemobejk@gmail.com> | |
| Wed, 29 Aug 2012 08:17:31 +0000 (29 11:17 +0300) | ||
| committer | Stefan Becker <chemobejk@gmail.com> | |
| Thu, 30 Aug 2012 19:04:32 +0000 (30 22:04 +0300) | ||
| tree | c0ad3f3f693da0f31f69f9a59d409fdda5d29cc7 | treesnapshot (tar.gz zip) |
| parent | 4e2f7587c53877b93f412fdee22fe49b512809af | commitdiff |
telepathy: always check cancel in transport async ops
Successful completion of an asynchronous operation might already be
queued in the main event loop when disconnect is called on the
transport. That means that just checking for an error return is not
enough to ensure that the transport is still valid.
Also reordered freeing up of the transport data structure to make sure
we are not leaking the cancel object.
Successful completion of an asynchronous operation might already be
queued in the main event loop when disconnect is called on the
transport. That means that just checking for an error return is not
enough to ensure that the transport is still valid.
Also reordered freeing up of the transport data structure to make sure
we are not leaking the cancel object.
| src/telepathy/telepathy-transport.c | diffblobblamehistory |