Bug 39399 - Assert on freeing invalid object
Summary: Assert on freeing invalid object
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: 0.12
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-20 05:26 UTC by vincent
Modified: 2019-12-03 19:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
log showing the assert (23.67 KB, application/x-bzip)
2011-07-20 05:27 UTC, vincent
Details
stack trace at assert (8.64 KB, application/octet-stream)
2011-07-20 05:28 UTC, vincent
Details

Description vincent 2011-07-20 05:26:56 UTC
I was connected to a gtalk account from meego-app-im, and repeatedly starting/ending calls between it and another gtalk account with empathy on a remote machine, to try to repro some other bug.
I'm not sure exactly at what point of this procedure gabble hit that assert. See attached logs and bt.
Note the warnings about CRC mismatch at the start of the bt. I installed debug info after the crash to have a better stack trace, so it may be off if packages were replaced in the repos.

Using version 0.12.2-16,4 as packaged on meego, so not so up to date code, but filing this anyway, as I never saw this before so probably hard to repro/check if fixed in new version.
Comment 1 vincent 2011-07-20 05:27:46 UTC
Created attachment 49338 [details]
log showing the assert
Comment 2 vincent 2011-07-20 05:28:27 UTC
Created attachment 49339 [details]
stack trace at assert
Comment 3 GitLab Migration User 2019-12-03 19:53:28 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/170.


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.