Ubuntu
kdenetwork package

Kopete begins to use 95%cpu and becomes unresponsive.

Bug #34040 reported by Aaron Hedch
14
Affects Status Importance Assigned to Milestone
kdenetwork (Ubuntu)
Invalid
Medium
tanranger

Bug Description

For no reason that I can think of, kopete begins to take up 95% cpu. I have the history plugin loaded and am using the MSN protocol. Only happens when a conversation window is open.

Kenny Duffus (kduffus)
Changed in kdenetwork:
assignee: nobody → kubuntu-team
Revision history for this message
Andres Mujica (andres.mujica) wrote :

i've got a similar problem to this

i've noticed it ocurrs when someone sent a message and you haven't checked it.

Revision history for this message
Torsten Knodt (torsknod) wrote :

I have the same problem and it's really frustrating. I remeber that over a year ago I read something about this in a kde mailing list. There was a discussion that the log files seem to be fully parsed into a DOM tree and that would be the performance problem. I don't know if this is all, as I even wait up to 15 seconds on my amd64 system. Java Xerces is even on my 1Ghz x86 system so fast, that I don't recognize the delay.

Revision history for this message
Sridhar Dhanapalan (sridhar) wrote :

This is still a problem in Kubuntu 7.04. It seems to occur when I'm logged into an MSN account, and it stops immediately after I log out. I also use Kopete with XMPP, and it doesn't have this problem.

Changed in kdenetwork:
status: Unconfirmed → Confirmed
Sarah Kowalik (hobbsee-deactivatedaccount)
Changed in kdenetwork:
assignee: kubuntu-team → mattr
Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom reproducible in current 8.04 or 8.10 alpha?

Changed in kdenetwork:
status: Confirmed → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!
Probably not an issue in Intrepid either.

Changed in kdenetwork:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.