Bug 477517

Summary:	modification of every next mp3 tag require more time as modification of previous tag
Product:	[Fedora] Fedora	Reporter:	Sergei LITVINENKO <sergei.litvinenko>
Component:	amarok	Assignee:	Aurelien Bompard <gauret>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	10	CC:	gauret, rdieter, tuxbrewr
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-12-31 16:59:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sergei LITVINENKO 2008-12-21 14:02:26 UTC

Description of problem:
First several tags can be modified quick, but every next modification require more and more time. Usage of CPU is 100%  

Version-Release number of selected component (if applicable):
amarok-2.0-2.fc10.i386

How reproducible:
Step by step modify 10-20 tags in collection

Steps to Reproduce:
1. Open the collection
2. Add to the play list (right window) 20 songs.
3. modify tags for every (by "edit track detail", "Save & Close")
  
Actual results:
Amarok freezes for a long time (interface is unaccessible) after "Save & Close" for 10-th and next track.

Expected results:
Amarok finalize modification of tag quick.

Additional info:
Restart Amarok help to continue...

Comment 1 Rex Dieter 2008-12-21 22:12:17 UTC

Looks like an excellent candidate to report upstream to bugs.kde.org.

Comment 2 Rex Dieter 2008-12-31 16:59:43 UTC

Reportedly fixed in svn and for 2.0.1, we'll continue to track this upstream.