Elliott Sales de Andrade
qulogic at pidgin.im
Thu Oct 7 13:42:19 EDT 2010
On Thu, Oct 7, 2010 at 7:18 AM, Florian Quèze <florian at instantbird.org>wrote:
> Libpurple has been upgraded from 2.6.6 (which was used for Instantbird
> 0.2) to 2.7.3 in nightly builds of Instantbird about two weeks ago, so
> the crash data that we collect may be relevant again to you.
> Our crash reports database can be queried at
> I've checked the data this morning and if we except the uninteresting
> reports (very old versions, crashes in plugins that we know nothing
> about, ...) and the netsoul plugin crashes (already fixed, the bug was
> trivial), we are currently seeing at least 2 (or 3) crashes in
> libpurple that probably deserve some attention: 1 (or 2) new crashes
> in MSN (may be somewhat related to upnp) and one in oscar, that was
> already in libpurple 2.6.6.
> - We have a null-printf crash in msn_slpmsg_sip_new. From what I've
> been told it usually happens within 2 minutes of the connection of an
> MSN account.
> We also have crash reports where it happened with a much longer
> uptime, but the delay may be because the user has manually connected
> the MSN account.
> The stack is
> More reports of the same issue (the stacks are very similar, if not
> completely identical):
I've quickly narrowed it down to two of the inputs to that function, but the
best bet for figuring it out would be a debug log with the
PURPLE_VERBOSE_DEBUG env var set. It may be related to the one below,
though, since it tends to cause weird things to happen.
> - We have a significant number of crashes in
> msn_slp_sip_recv/msn_dc_destroy/purple_network_listen_cancel, with
> variations in the stacks. I suspect the variations may be randomly
> caused by using already free'd memory.
> Some stacks for this problem:
> This seems similar to http://developer.pidgin.im/ticket/12387 I'll try
> to apply the patch available there, and we will see if it disappears
> in the next nightlies.
Definitely will be fixed by #12387.
> - the oscar plugin crashes in flap_connection_destroy_cb:
> For more similar stacks, see
> Some variations:
> The crashes that are in version 0.2 of Instantbird are with libpurple
> 2.6.6, the less-than-two-weeks-old crashes of version 0.3a1pre are
> with libpurple 2.7.3.
> >From what I've been told by users, this crash happens mostly when a
> laptop wakes up from sleep and is connected to a different network.
> It seems flap_connection_destroy_cb is called from a timeout after the
> connection has already been destroyed.
> I've already shown this crash in #pidgin a few months ago and it was
> suggested that https://hg.instantbird.org/instantbird/rev/f2d45147098b
> may fix it, but the crash reports we are still getting show it still
> isn't fixed.
> This looks like what is described in
> http://developer.pidgin.im/ticket/5927 I left a comment there. I'm
> surprised it's still not fixed after 2 years given how common it seems
> to be (it was the most common libpurple crash in Instantbird 0.2), but
> maybe the frequency of the crash wasn't known, or has increased
> I hope this data will be useful to you.
> If these crashes are already known, please let me know if there's some
> info I've missed about them or potential fixes in Trac that I should
> Florian Quèze
Elliott aka QuLogic
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel