Summary: | Crashes if a PEP alias request and a PEP location request are outstanding when we disconnect | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Will Thompson <will> |
Component: | gabble | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | ken.vandine |
Version: | 0.10 | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Will Thompson
2010-09-29 09:07:41 UTC
(In reply to comment #0) > • but gabble_vcard_manager_request() blows up when trying to send the request > because the connection's request pipeline pointer was set to NULL *before* > being unreffed (since that's how tp_clear_object() works). I think if gabble_vcard_manager_request (actually request_send, but in your build it must have been inlined?) relies on conn->req_pipeline, it should survive conn->req_pipeline being NULL (and trigger TP_ERROR_DISCONNECTED, or equivalent, immediately or in an idle). An alternative would be for the GabbleVCardManager to have its own ref to the pipeline, to make the unwinding happen in the expected order. We have a user that I think is seeing this same crash on Maverick. https://bugs.launchpad.net/telepathy-gabble/+bug/668306 (I think Simon may have fixed this? Someone (maybe me later when I read this mail) should check it out.) I think this was fixed way back in 0.11.2, at the branch ending at 5666efa919d6b. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.