[Bug 22682] New: Rare assertion failure in TpProxyPendingCall when DBusGProxyCall is NULL
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Jul 9 11:01:28 CEST 2009
http://bugs.freedesktop.org/show_bug.cgi?id=22682
Summary: Rare assertion failure in TpProxyPendingCall when
DBusGProxyCall is NULL
Product: Telepathy
Version: unspecified
Platform: Other
URL: http://git.collabora.co.uk/?p=user/smcv/telepathy-glib-
smcv.git;a=shortlog;h=refs/heads/assertion
OS/Version: All
Status: NEW
Keywords: patch
Severity: normal
Priority: medium
Component: telepathy-glib
AssignedTo: telepathy-bugs at lists.freedesktop.org
ReportedBy: simon.mcvittie at collabora.co.uk
commit 87cef643afd5143795871cc7de0b50cd2fde51f5
Author: Simon McVittie <simon.mcvittie at collabora.co.uk>
Date: 2009-07-09 09:53:14 +0100
TpProxyPendingCall: fix rare crash when cancelled before we've been given
our DBusGProxyCall
One of the telepathy-mission-control regression tests hit an assertion
failure in dbus_g_proxy_cancel_call (., call=0x0), with
tp_proxy_pending_call_lost_weak_ref on the stack. As far as I can tell,
this can only happen if the weak_object is finalized before
tp_proxy_pending_call_v0_take_pending_call is called, which seems unlikely
but possible.
This happened 2 out of 3 times when running distcheck on MC 5.1.4 (but not when
running the tests normally - a timing issue?), and seems to be fixed by using
this telepathy-glib build.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the telepathy-bugs
mailing list