HistorySaveThread sometimes causes delay and crash on Kadu exit
As summary. Fixed in Git commit: f75b70e1 Steps to reproduce: Unknown. Additional information: Sometimes it looks like that:
Fatal: ASSERT failure in QMutex::unlock(): "A mutex must be unlocked in the same thread that locked it.", file thread/qmutex.cpp, line 370
backtrace: ('fatal error from Qt (above)') ======= BEGIN OF BACKTRACE ===== [0] /home/beevvy/kadu-inst/bin/kadu(_Z14printBacktraceRK7QString+0xa4) [0x70de28] [1] /home/beevvy/kadu-inst/bin/kadu() [0x57746f] [2] /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x1e) [0x7f5528a1f12e] [3] /usr/lib64/qt4/libQtCore.so.4(+0x6d371) [0x7f5528a1f371] [4] /usr/lib64/qt4/libQtCore.so.4(_Z6qFatalPKcz+0x99) [0x7f5528a1f4e9] [5] /usr/lib64/qt4/libQtCore.so.4(_ZN6QMutex6unlockEv+0x39) [0x7f5528a251f9] [6] /home/beevvy/kadu-inst/bin/kadu(_ZN12QMutexLocker6unlockEv+0x43) [0x57cb8d] [7] /home/beevvy/kadu-inst/bin/kadu(_ZN12QMutexLockerD1Ev+0x18) [0x57cb48] [8] /home/beevvy/kadu-inst/lib/kadu/plugins/libhistory.so(_ZN17HistorySaveThread3runEv+0x208) [0x7f550f1140d0] [9] /usr/lib64/qt4/libQtCore.so.4(+0x78b9e) [0x7f5528a2ab9e] [10] /lib64/libpthread.so.0(+0x6d4c) [0x7f55271f0d4c] [11] /lib64/libc.so.6(clone+0x6d) [0x7f55274de58d] ======= END OF BACKTRACE ====== Aborted
And sometimes it is a message about busy QWaitCondition. I will post it when it will happen again.
(from redmine: created on 2011-08-03, closed on 2011-12-11)