[Konversation-devel] [Bug 163752] 100% cpu when network goes down (ping timeout)

[Maxime Gamboni]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=163752         




------- Additional Comments From maxime gamboni org  2008-06-12 05:58 -------
I installed the svn version and the bug still seems to be there. The "about" window now says Konversation 1.0.1+ #3233 (using KDE 3.5.8).

I observed the behaviour more carefully now:

1. I'm logged in an irc channel and the connectivity goes down (pinging the server reports "destination host unreachable")

2. After a while, the latency display in Konversation starts counting seconds

3. Every now and then the status bar changes to say "no answer from server <server name> for more than X time" (for 5, 35, and 65 seconds)

4. When the latency counter hits 128 seconds, the message "[error]  Closing Link: <my handle and ip> (Ping timeout)" appears, and the cpu usage goes up to 100%. The list of people being connected is still visible.

5. The latency counter keeps counting, and the status bar keeps updating the "no answer" message (for 140, 170 and 175 seconds). All this time, cpu usage is at 100%.

6. When the latency counter hits 180, the message "konversation: Connection broken (Socket fd -1) 0!" is sent to stdout (maybe stderr), the nick list on the right is blanked and cpu usage is normal again.

Thanks.