#175: libpurple API called from different threads
-----------------------+-------------------------
Reporter: cavedon | Owner: vadim
Type: defect | Status: reopened
Priority: critical | Milestone: QuteCom 3.0
Component: misc | Version: 2.2
Resolution: | Keywords:
OS: all |
-----------------------+-------------------------
Comment (by cavedon):
Unfortunately the problem is not fixed.
Libpurple is not being used according to the specification. According to
the docs, all API functions must be called from the same thread. However
this is not true on QuteCom.
Apparently when a private copy of libpurple is used, this is not causing
big issues. But when system libpurple is used, it makes qutecom crash qt
logout in some case. I posted two patches to fix the isssue, but for some
reason I was not able to understand, the second patch causes memeory
corruption. A summary of the status is at comment:12
--
Ticket URL: <http://trac.qutecom.org/ticket/175#comment:15>
QuteCom <http://trac.qutecom.org>
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
