Version: 0.11 beta 2 (using KDE KDE 3.4.92) Installed from: Mandriva RPMs I closed an IRC chat channel window, and Kopete 0.11 beta 2 crashed with this backtrace: Using host libthread_db library "/lib/tls/libthread_db.so.1". `shared object read from target memory' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1243433280 (LWP 4025)] [KCrash handler] #4 Kopete::ChatSession::members (this=0x0) at kopetechatsession.cpp:177 #5 0xb55792ac in IRCContact::qt_invoke (this=0x8678988, _id=27, _o=0x8678988) at irccontact.moc:163 #6 0xb55809b4 in IRCChannelContact::qt_invoke (this=0x8678988, _id=27, _o=0xbfb0c31c) at ircchannelcontact.moc:152 #7 0xb6a44f6f in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #8 0xb55695b9 in IRCContactManager::privateMessage (this=0x8407f88, t0=0x0, t1=0x0, t2=@0x0) at irccontactmanager.moc:169 #9 0xb5584502 in IRCContactManager::slotNewMessage (this=0x8407f88, originating=@0x0, channel=@0x0, message=@0x840e728) at irccontactmanager.cpp:99 #10 0xb558475d in IRCContactManager::qt_invoke (this=0x8407f88, _id=10, _o=0xbfb0c42c) at irccontactmanager.moc:183 #11 0xb6a45009 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #12 0xb55a7963 in KIRC::Engine::incomingMessage (this=0x840e728, t0=@0x0, t1=@0x0, t2=@0x0) at kircengine.moc:1431 #13 0xb55b0f0b in KIRC::Engine::privmsg (this=0x840e728, msg=@0xbfb0c694) at kircengine_commands.cpp:282 #14 0xb55ae3f9 in KIRC::Engine::qt_invoke (this=0x840e728, _id=82, _o=0xbfb0c5f4) at kircengine.moc:2045 #15 0xb6a45009 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0xb55ba335 in KIRC::MessageRedirector::redirect (this=0x83fc830, t0=@0x0) at kircmessageredirector.moc:95 #17 0xb55ba5ba in KIRC::MessageRedirector::operator() (this=0x83fc830, msg=@0xbfb0c694) at kircmessageredirector.cpp:47 #18 0xb55ab2dd in KIRC::Engine::slotReadyRead (this=0x840e728) at kircengine.cpp:371 #19 0xb55ae14a in KIRC::Engine::qt_invoke (this=0x840e728, _id=66, _o=0xbfb0c818) at kircengine.moc:2029 #20 0xb6a45009 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0xb6a45538 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0xb71097f9 in KAsyncIO::readyRead () from /usr/lib/libkdecore.so.4 #23 0xb71ef51f in KExtendedSocket::socketActivityRead () from /usr/lib/libkdecore.so.4 #24 0xb71ef72b in KExtendedSocket::qt_invoke () from /usr/lib/libkdecore.so.4 #25 0xb6a45009 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #26 0xb6a456f4 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #27 0xb6de410f in QSocketNotifier::activated () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0xb6a686c5 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #29 0xb69d7ec0 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #30 0xb69d88cf in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #31 0xb71cde2e in KApplication::notify () from /usr/lib/libkdecore.so.4 #32 0xb69ca46b in QEventLoop::activateSocketNotifiers () from /usr/lib/qt3/lib/libqt-mt.so.3 #33 0xb697abd8 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #34 0xb69f1e29 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #35 0xb69f1d24 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #36 0xb69d771c in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #37 0x08080fd0 in main (argc=0, argv=0x0) at main.cpp:103
I can confirm. The problem can for example appear when one is leaving from a large channel, the one I tested had about 1000 users. I guess because the channel destruction takes several seconds on modern hardware, there is good chance that we receive some messages for the channel at the wrong time. libkopete: [virtual KopeteChatWindow::~KopeteChatWindow()] libkopete: [void Kopete::ChatSessionManager::removeSession(Kopete::ChatSession*)] kopete (irc - raw protocol): (23 bytes) >> PART #rap-albums :--- libkopete: [virtual Kopete::MessageHandlerChain::~MessageHandlerChain()] libkopete: [virtual Kopete::MessageHandlerChain::~MessageHandlerChain()] kopete (irc - raw protocol): << :someuser!user@Rizon-243A05E9.host PRIVMSG #rap-albums :... kopete (irc): #rap-albums has codec 0x81389e8 KCrash: Application 'kopete' crashing...
*** Bug 122915 has been marked as a duplicate of this bug. ***
*** Bug 130124 has been marked as a duplicate of this bug. ***
*** Bug 131409 has been marked as a duplicate of this bug. ***
*** Bug 136803 has been marked as a duplicate of this bug. ***
*** Bug 139486 has been marked as a duplicate of this bug. ***
seems to be a popular bug :) ... for me it is the reason not to use kopete for IRC. by the way: the channels that crash my kopete usually have >50 users what about just introducing a waiting time, when kopete waits that the channel terminates? this would solve this crash, right?
*** This bug has been marked as a duplicate of bug 104920 ***