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%).
Not conserve but consume of course, sorry my bad English.
*** This bug has been marked as a duplicate of bug 278897 ***
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?
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.
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
Indeed, when the context view doesn't contain any widgets and is hidden, the bug does not appear.
*** Bug 278245 has been marked as a duplicate of this bug. ***
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.
same here
This might be related to bug 278897
yes it is, by the looks of it. *** This bug has been marked as a duplicate of bug 278897 ***