Bug 282006

Summary:	Amarok - high resource usage after start
Product:	[Applications] amarok	Reporter:	Marek Ruszkowski <aaatoja>
Component:	general	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	2.4.3
Target Milestone:	2.5
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Marek Ruszkowski 2011-09-14 11:19:16 UTC

Version:           2.4.3 (using KDE 4.7.1) 
OS:                Linux

Every time I start Amarok I got 100% CPU:
7656 linux    20   0 1009m 111m  51m R   96  2.8   0:14.39 amarok 

I need to open amarok window, hit next/previous/something button to normalize. I'm not 100% sure but I think it started with 2.3.1.

Reproducible: Always

Steps to Reproduce:
1. Start amarak
2. Watch amarok process
3. Hit next track button

Actual Results:  
100% CPU before step 3.

Expected Results:  
Standard CPU consumption.

Comment 1 Myriam Schweingruber 2011-09-16 10:18:53 UTC

Is Amarok minimized in the tray when you start?
Which elements of the Context View do you use?
Do you use external scripts?

Comment 2 Marek Ruszkowski 2011-09-16 11:00:53 UTC

Amarok is minimized on start. Context view is disabled (view blocked, Slim Toolbar). By default, after start Local Collection selected. OSD disabled.

[Plugins]
Amarok Script ConsoleEnabled=false
Cool StreamsEnabled=true
Librivox.orgEnabled=true
LyricWikiEnabled=true
amarok_service_ampacheEnabled=false
amarok_service_jamendoEnabled=true
amarok_service_lastfmEnabled=true
amarok_service_magnatunestoreEnabled=false
amarok_service_mp3tunesEnabled=false
amarok_service_opmldirectoryEnabled=false

Comment 3 Marek Ruszkowski 2011-09-16 11:09:39 UTC

I have disabled all plugins and scripts, unlocked toolbar and switched to standard view but with no effect.

Comment 4 Myriam Schweingruber 2011-09-16 11:22:56 UTC

Thank you for the feedback.
Even with the Context View disabled, if there are loaded applets those should be removed before disabling it.

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