Amarok eats CPU when idling

Bug #200212 reported by Christophe Painchaud
4
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: amarok

Hello,

I have a brand new installation of Ubuntu Hardy , with latest updates. I am using KDE3 desktop from official mirrors. I noticed that Amarok is constantly using from 5 to 12% of my CPU (Core Duo), no only durin my session startup but all the time, even hours after my session start.

Amarok is configured to start with my KDE session, it starts eating CPU as soon it starts. If I open amarok window, CPU load goes a bit higher, then if I close window or minimize, it stops eating CPU at all. If I open window again, CPU is used again.

Here is normal a normal strace (when it doesn't eat CPU) they happen 2/3 times per second:
read(5, 0x808fa1c, 4096) = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1205076838, 246831}, NULL) = 0
select(26, [5 6 7 10 12 14 16 18 20 23 25], [], [], {0, 198383}) = 0 (Timeout)
gettimeofday({1205076838, 446532}, NULL) = 0
gettimeofday({1205076838, 446640}, NULL) = 0
read(5, 0x808fa1c, 4096) = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1205076838, 446780}, NULL) = 0
select(26, [5 6 7 10 12 14 16 18 20 23 25], [], [], {0, 198434}) = 0 (Timeout)
gettimeofday({1205076838, 646537}, NULL) = 0
gettimeofday({1205076838, 646738}, NULL) = 0
read(5, 0x808fa1c, 4096) = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1205076838, 646864}, NULL) = 0
select(26, [5 6 7 10 12 14 16 18 20 23 25], [], [], {0, 198350}) = 0 (Timeout)
gettimeofday({1205076838, 846538}, NULL) = 0
gettimeofday({1205076838, 846642}, NULL) = 0

Now when Amarok starts eating CPU, its spamming system calls like hundreds per second:
gettimeofday({1205076930, 687552}, NULL) = 0
select(6, [5], [5], NULL, NULL) = 1 (out [5])
writev(5, [{">\5\7\0\326\6@\2\325\6@\2\331\5@\2\0\0\0\0\0\0\0\0\332"..., 4088}, {">\5\7\0\327\6@\2\325\6@\2\331\5@\2\0\0$\0h\1%\0\4\0\0\0"..., 28}], 2) = 4116
select(6, [5], [5], NULL, NULL) = 1 (out [5])
writev(5, [{">\5\7\0001\7@\2\325\6@\2\331\5@\2\0\0\0\0m\1%\0\4\0$\0"..., 4088}, {">\5\7\0001\7@\2\325\6@\2\331\5@\2\0\0\0\0\332\2%\0\4\0"..., 28}], 2) = 4116
select(6, [5], [5], NULL, NULL) = 1 (out [5])
writev(5, [{">\5\7\0\327\6@\2\325\6@\2\331\5@\2\0\0$\0\332\2%\0\4\0"..., 4088}, {">\5\7\0\327\6@\2\325\6@\2\331\5@\2\0\0$\0G\4%\0\4\0\0\0"..., 28}], 2) = 4116
select(6, [5], [5], NULL, NULL) = 1 (out [5])
writev(5, [{">\5\7\0001\7@\2\325\6@\2\331\5@\2\0\0\0\0L\4%\0\4\0$\0"..., 4088}, {">\5\7\0`\1@\2\325\6@\2\331\5@\2\0\0\0\0r\1%\0\4\0\2\0", 28}], 2) = 4116
select(6, [5], [5], NULL, NULL) = 1 (out [5])
writev(5, [{">\5\7\0`\1@\2\325\6@\2\331\5@\2\0\0\0\0w\1%\0\4\0\2\0>"..., 4088}, {">\5\7\0`\1@\2\325\6@\2\331\5@\2\0\0\0\0Q\4%\0\4\0\2\0", 28}], 2) = 4116
gettimeofday({1205076930, 691621}, NULL) = 0
select(6, [5], [5], NULL, NULL) = 1 (out [5])
writev(5, [{">\5\7\0`\1@\2\325\6@\2\331\5@\2\0\0\0\0V\4%\0\4\0\2\0>"..., 980}], 1) = 980
read(5, 0x808fa1c, 4096) = -1 EAGAIN (Resource temporarily unavailable)

Tell me if you need more informations.

My ubuntu version:
root@icare:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

Revision history for this message
Luis Silva (lacsilva) wrote :

Try to shut down visualisations. It reduced my cpu usage.

Revision history for this message
Christophe Painchaud (dash-ionblast) wrote :

Hello, I did that already to reduce CPU consumption (by half), but the right solution is to fix amarok. That's why I am filling a bug :)

Revision history for this message
Harald Sitter (apachelogger) wrote :

Then you should file the Bug for Amarok itself on http://bugs.kde.org

Anyway, this issue will be addressed by the Amarok project in the upcoming Amarok 2 series, so I will close this report because we can't know yet how Amarok 2 will behave in this area.

Changed in amarok:
status: New → Invalid
Revision history for this message
Christophe Painchaud (dash-ionblast) wrote :

that's fair :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.