Version: 2.4.0 (using KDE 4.5.5) OS: Linux When Amarok is open (not minimized) and reproducing a song, I get ~30% cpu consumption on the X process. This stops as soon as I minimize Amarok, or simply press the pause button. After some tests, I think I've narrowed it down to the progress bar. Reproducible: Always Steps to Reproduce: Open Amarok, play a song, don't minimize the window. Actual Results: X process takes a ~30% usage of the cpu. Expected Results: Keep the X process at low cpu consumption. This stops happening when you minimize the window or just play pause. Here's why I think this is due to the progress bar: just de-attach the top bar (the one that contains the progress bar and the play/pause buttons) and let it "float" somewhere. Then, set the focus on another window. This causes the "floating" bar to disappear, while the song keeps playing. The X cpu usage drops dramatically. BTW, I'm using the the proprietary Nvidia driver (v. 260.19.29).
That sounds like a graphic driver problem, can't reproduce this here though, I have a Radeon card and don't see X peaking because of Amarok, but because of Plasma.
I'm not saying it isn't a graphic driver problem, but why doesn't it happen with other progress bars, such as the one in smplayer? (when it just plays audio, so that there's no video peaking the X process) I've reproduced this bug on another computer, but it also has a Nvidia card with the proprietary driver, so no new clues there. To add more information pointing towards the progress bar, I've noticed that the X peaking gets worse the wider the Amarok window is (i.e. the bar is longer too, so the slider needs to move faster).
This is an automated message from the triager: Amarok 2.4.1 has been released on May 8 already. Could you please upgrade and test if you can still reproduce this bug? Without feedback within a month we will close this bug as resolved. Thank you for your understanding.
It got better since my original report. Now X gets about 8-10% of the cpu, compared to the previous ~30%. I've upgraded the NVidia driver (now 270.41.06), KDE (now 4.6.3) and Amarok (now 2.4.1) over the last months, so I'm not sure which one's to thank. However, I still think there's some issue there that's worth investigating, because 8-10% is too much for a progress bar. With Smplayer's and Kaffeine's progress bars running, X just gets 1% of the cpu. Thanks!
Thank you for the feedback.
*** This bug has been marked as a duplicate of bug 244896 ***