Summary: | crash when closing IRC chat channel | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | Frederik Himpe <fhimpe> |
Component: | IRC Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | damir.perisa, kde, marc.collin, mcepl, sven.burmeister |
Priority: | NOR | ||
Version First Reported In: | 0.40.0 | ||
Target Milestone: | --- | ||
Platform: | Mandriva RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Frederik Himpe
2005-11-06 17:43:38 UTC
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 *** |