Bug 279144

Summary:	Amarok uses 100% cpu if context view is hidden but there are some widgets
Product:	[Applications] amarok	Reporter:	valdikss
Component:	Context View	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bugs-kde, cc, frederic.coiffier, lfranchi, maxwux, oldium.pro, rdieter, schwarzer, simon.esneault
Priority:	NOR
Version:	2.4.3
Target Milestone:	2.5
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description valdikss 2011-08-02 09:47:42 UTC

Version:           2.4.3 (using KDE 4.7.0) 
OS:                Linux

Amarok uses 100% cpu you uncheck "context view" in "view" menu but there were some widgets when you did this.

Reproducible: Always

Steps to Reproduce:
1) Run amarok.
2) Uncheck "context view" in "view", leaving some widgets there.
3) Restart amarok.

Actual Results:  
Amarok conserves 100% cpu.

Expected Results:  
Amarok conserves CPU as normal (1-3%).

Comment 1 valdikss 2011-08-02 09:51:58 UTC

Not conserve but consume of course, sorry my bad English.

Comment 2 Myriam Schweingruber 2011-08-02 12:04:38 UTC


*** This bug has been marked as a duplicate of bug 278897 ***

Comment 3 Myriam Schweingruber 2011-08-03 00:26:44 UTC

You are of course right, this is not really related. Could you please run Amarok in debug mode and give us an output from the konsole?

Comment 4 valdikss 2011-08-03 03:45:23 UTC

I see nothing really interesting in the log.
http://paste.kde.org/105541/ Here is a log with context enabled, items(Wikipedia, lyrics, current song info) are there and amarok is minimised. 100% CPU.
http://paste.kde.org/105547/ Here is a log with context enabled but no items there and amarok is minimised. 1-3% CPU.
http://paste.kde.org/105553/ Here is a log with context disabled and no items there and amarok is minimised. 1-3% CPU.

And there is another bug. When you delete all the items, disable context then restart amarok, you have no way to add items again, the "settings" button is not on it's place anymore. I had to delete some amarok files from .kde4/share/config.

Comment 5 Bernhard Beschow 2011-08-03 09:31:50 UTC

I confirm this bug. I have the context view disabled and Amarok uses 100% CPU.

The mysterious part of the debug output (probably) is:

amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 2111x323) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 2111x323) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 2114x334) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 2114x334) associated screen is -1

...

amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 31076x106528) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 31079x106539) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 31079x106539) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 31079x106539) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 31079x106539) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 31082x106550) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 31082x106550) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 31082x106550) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 31082x106550) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 31085x106561) associated screen is -1
amarok(3379)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 31085x106561) associated screen is -1

Comment 6 Bernhard Beschow 2011-08-03 09:40:28 UTC

Indeed, when the context view doesn't contain any widgets and is hidden, the bug does not appear.

Comment 7 Myriam Schweingruber 2011-08-03 10:18:30 UTC

*** Bug 278245 has been marked as a duplicate of this bug. ***

Comment 8 SZÉKELYI Szabolcs 2011-08-15 14:41:25 UTC

I can confirm this. I had the same problem. My context view was originally hidden, and Amarok used 100% CPU. Then I made the context view appear, removed all the widgets, and hid the context view again. The CPU usage immediately fell back to the normal value.

Comment 9 Max Wu 2011-09-04 00:02:26 UTC

same here

Comment 10 Frederik Schwarzer 2011-09-05 17:01:24 UTC

This might be related to bug 278897

Comment 11 Rex Dieter 2011-09-30 20:42:51 UTC

yes it is, by the looks of it.

*** This bug has been marked as a duplicate of bug 278897 ***