Bug 157827 - plasma uses 100% of cpu with knewticker
Summary: plasma uses 100% of cpu with knewticker
Status: RESOLVED NOT A BUG
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-14 16:41 UTC by Cade Robinson
Modified: 2009-01-20 20:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cade Robinson 2008-02-14 16:41:01 UTC
Version:            (using KDE 4.0.1)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Plasma uses more and more cpu the more news feeds I add to the newsticker plasmoid.
On average about 20%-30% per feed.

When adding feeds the icons for the feeds are not showing with the config window open.  I add about 5-8 feeds and cpu usage of plasma is about 75%.
Once I hit "OK" and the icons fill in for the feeds cpu shoots to 100%.

Once I close the newsticker plasmoid cpu usage goes back to normal.
Comment 1 Aaron J. Seigo 2008-02-14 17:38:00 UTC
this would be a knewsticker bug (it has its own component) in bugs.kde.org. however, it's not actually a knewsticker bug, it's an upstream bug in Qt. Trolltech is aware of it and working on a solution.
Comment 2 Cade Robinson 2008-02-14 17:42:09 UTC
Thanks for the info.


On 14 Feb 2008 16:38:01 -0000, Aaron J. Seigo <aseigo@kde.org> wrote:
[bugs.kde.org quoted mail]
Comment 3 Raúl 2008-02-29 01:42:25 UTC
Hello, I'm hitting this bug as well, and quite the same situation as bug reporter, any news about it?

It looks like it's only appearing when I use kwin effects. I'm on an intel video card with latest video driver and mesa 7.0.3-rc2.

I could provide backtraces and more info on request.

Thanks.
Comment 4 Peter 2009-01-20 20:25:29 UTC
I have the same problem.
when I use knewsticker plasma have 100% cpu usage with a:
Intel(R) Core(TM)2 Duo CPU     E8200  @ 2.66GHz
I think that cannot be normal??