Bug 138898 - kopete freezes after receivng new gadu message
Summary: kopete freezes after receivng new gadu message
Status: RESOLVED NOT A BUG
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: knetwork (show other bugs)
Version: 3.5
Platform: Gentoo Packages Linux
: LO normal
Target Milestone: ---
Assignee: Thiago Macieira
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-17 00:50 UTC by Karol Jurak
Modified: 2008-05-05 14:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karol Jurak 2006-12-17 00:50:51 UTC
Version:           0.12.3 (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages
Compiler:          gcc 4.1.1 CFLAGS="-march=pentium4 -O2" CXXFLAGS="-march=pentium4 -O2"
OS:                Linux

Kopete sometimes freezes after receiving new gadu message (not every message, just the one that starts the chat). It shows the balloon but clicking on "View" does nothing - kopete becomes unresponsive.

Here's the backtrace:

#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb643b67e in __lll_mutex_lock_wait () from /lib/libpthread.so.0
#2  0xb64382b3 in _L_mutex_lock_49 () from /lib/libpthread.so.0
#3  0xb6cb8c00 in ?? () from /usr/qt/3/lib/libqt-mt.so.3
#4  0xbfe529d8 in ?? ()
#5  0xbfe52a60 in ?? ()
#6  0xb702e558 in ?? ()
#7  0xb6e3e867 in ?? () from /usr/kde/3.5/lib/libkdecore.so.4
#8  0x002321f0 in ?? ()
#9  0xb6cb8c00 in ?? () from /usr/qt/3/lib/libqt-mt.so.3
#10 0xbfe52a38 in ?? ()
#11 0x083af028 in ?? ()
#12 0xbfe529f8 in ?? ()
#13 0xb6b1c54c in QRealMutexPrivate::lock () from /usr/qt/3/lib/libqt-mt.so.3
#14 0xb6b1c54c in QRealMutexPrivate::lock () from /usr/qt/3/lib/libqt-mt.so.3
#15 0xb6b1c3da in QMutex::lock () from /usr/qt/3/lib/libqt-mt.so.3
#16 0xb7d1594a in QMutexLocker (this=0xfffffffc, m=0xb6440ff4) at qmutex.h:96
#17 0xb6fc0db5 in KNetwork::Internal::KResolverManager::dequeue (this=0x83af028, obj=0x8444f48)
    at kresolvermanager.cpp:820
#18 0xb6fbfa86 in KNetwork::KResolver::cancel (this=0x8444f48, emitSignal=false)
    at kresolver.cpp:510
#19 0xb6fbfe6e in ~KResolver (this=0x8444f48) at kresolver.cpp:307
#20 0xb6f75f57 in ~KExtendedSocketPrivate (this=0x8444f08) at kextsock.cpp:63
#21 0xb6f74ff0 in ~KExtendedSocket (this=0x843dea0) at kextsock.cpp:222
#22 0xb6eec92c in ~KServerSocket (this=0x843a428) at ksock.cpp:428
#23 0xb7489528 in ~Slave (this=0x843c690) at slave.cpp:187
#24 0xb7488638 in KIO::Slave::holdSlave (protocol=@0x83e1a18, url=@0x84431a8) at slave.cpp:505
#25 0xb7491283 in KIO::Scheduler::findIdleSlave (this=0x8415948, job=0x8443130, 
    exact=@0xbfe52d7b) at scheduler.cpp:492
#26 0xb7491cbf in KIO::Scheduler::startJobScheduled (this=0x8415948, protInfo=0x83e0768)
    at scheduler.cpp:360
#27 0xb74932fe in KIO::Scheduler::startStep (this=0x8415948) at scheduler.cpp:278
#28 0xb749346a in KIO::Scheduler::qt_invoke (this=0x8415948, _id=4, _o=0xbfe52e48)
    at scheduler.moc:161
#29 0xb68a4700 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#30 0xb68a5240 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#31 0xb6bb58a9 in QTimer::timeout () from /usr/qt/3/lib/libqt-mt.so.3
#32 0xb68c56b0 in QTimer::event () from /usr/qt/3/lib/libqt-mt.so.3
#33 0xb684a10c in QApplication::internalNotify () from /usr/qt/3/lib/libqt-mt.so.3
#34 0xb684ac27 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#35 0xb6ebadf1 in KApplication::notify (this=0xbfe5332c, receiver=0x8415970, event=0xbfe53104)
    at kapplication.cpp:550
#36 0xb683ff5a in QEventLoop::activateTimers () from /usr/qt/3/lib/libqt-mt.so.3
#37 0xb67fd6aa in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3
#38 0xb685f9bd in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#39 0xb685f862 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#40 0xb6849c3d in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#41 0x0807451b in main (argc=Cannot access memory at address 0x0
) at main.cpp:107
Comment 1 Thiago Macieira 2007-06-09 12:37:13 UTC
The line numbers are garbled. There is no call to QMutexLocker at kresolvermanager.cpp:820. That way, I can't know which mutex is deadlocking.
Comment 2 Thiago Macieira 2007-06-09 12:38:35 UTC
Also, please get me the backtrace of all threads (gdb command: thread apply all backtrace).
Comment 3 FiNeX 2008-05-05 13:02:54 UTC
Is this bug still reproducible?

Karol please could you answer to the Thiago question?

Otherwise we could close this bug: one year without giving any feedback should be enough :)
Comment 4 Karol Jurak 2008-05-05 14:24:30 UTC
Sorry for not providing any feedback. You can close this bug as I don't use Kopete any more and I'm no longer interested in resolving this issue.
Comment 5 FiNeX 2008-05-05 14:29:08 UTC
Closed