Bug 129376 - 100% cpu load when preferences opened
Summary: 100% cpu load when preferences opened
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: Audio/Video Plugin (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 133168 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-06-18 19:09 UTC by Marcin Orlowski
Modified: 2008-01-24 05:59 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marcin Orlowski 2006-06-18 19:09:09 UTC 
Version:           0.11.92 (0.12 Beta 1) (using KDE 3.5.2, Kubuntu Package 4:3.5.2-0ubuntu18 dapper)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-25-386

Opening Kopete preference window raises cpu load to 100% and keeps it that high unless preferences window is opened. Closing it cools down CPU.
Comment 1 Philip Rodrigues 2006-06-19 18:53:54 UTC 
I get 100% CPU usage on the 'Devices' tab, but not the others.
Comment 2 Andreas Kling 2006-08-29 11:51:31 UTC 
*** Bug 133168 has been marked as a duplicate of this bug. ***
Comment 3 Thomas Tanghus 2006-08-29 14:04:37 UTC 
Bug #133168 wasn't exactly a duplicate as it freezes the entire system and I have to do a hard reset
Comment 4 Thomas Tanghus 2006-08-29 18:10:58 UTC 
Found out that this only happens when I use kubuntus xserver-xorg-air-core
Comment 5 Marcin Orlowski 2006-09-23 20:56:01 UTC 
I was never using xserver-xorg-air-core (nor I do see such package here?).
Comment 6 Philip Rodrigues 2007-09-12 00:17:44 UTC 
*** Bug 149718 has been marked as a duplicate of this bug. ***
Comment 7 Cláudio da Silveira Pinheiro 2008-01-24 05:59:14 UTC 
Based on the fact Kopete's video code had huge improvements since this bug was issued, I'm closing this bug with the belief this problem doesn't exist anymore, as I was unable to reproduce it with current 3.5.x, 4.0.x and trunk versions.
If this is still an issue to you, please reopen this bug.