100% cpu usage

I am getting the same here

Amarok 1.4.7 (Using KDE 3.5.8) on Kubuntu Gutsy (7.10) - dist upgrade from 7.04
I tuned off "Watch folders for changes" under the "Configure Collection" Option group, and the problem does not go away, I don't get the "Updating Collection..." message anymore. I still get the 100% cpu usage by Amarok.

This seems to happen more when I play a song I have never played before.

This happens even when amarok is paused

$ uname -a
Linux nandrew79 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

I told amarok to do a full scan of my collection, and that seems to have fixed this problem
 Tools->Rescan Collection

I have not had amarok use much cpu for about an hour since changing the setting.

I was also able to re-enable the "Watch folders for changes" option.

"Rescan Collection" didnt do it for me.
I ran amarokcollectionscanner from console and it got stock on some itunes transmorgified song. Maybe the tool's got some problem with the stuff apple's doing to the comments field.

hth, Axel

I think your problem may be something to do with itunes, but I do not use it to test.

My problems are completely gone after the full scan. Axelerator, are you getting the 100% cpu usage, or is the scanner just stopping?

I was hoping we could close this bug, as it has not had any traffic for several months.

Can you let us know if it is just the one file, or several from itunes that are causing problems. I have noticed the collection scanner getting stuck on *.mp3 files that actually used mpeg layer 2 audio tracks, but these were created by another silly program. So could you check the files are actually mpeg layer 3 encoded, and perhaps that the id3 tags are all ok, and nothing funny

Thanks

Hi,

I tried some stuff and it seemed to resolve some stuff, which obviously doesnt help anyone but me.

But I have found a little trouble make which may be the/one cause for the problem. It's a broken file which is able to mess up amarok and the collectionscanner. Unfortunately the last output of the scanner has always been ( actually pretty logic thinking about it now) the last file before the broken one. I think s.th. went wrong during file transfer.

I attached the little bugger so you can toy with it. Mp3Blaster doesnt play it either of course - but it doesnt crash...

Well, it's a broken file, that is all to be said.
Amarok 2 will probably get an improved and more stable collectionscanner, can't promise that though, it also depends a lot on taglib really.

I would suggest that this bug should not be marked invalid, but rather fixed. This is because the original bug report (by Soren) was correct and confirmed by myself. It was only one user, Axelerator, whose problem was related to a broken file.
The original problem was that the collection scanner would stop at 91% when upgrading from 7.04 to 7.10.
The fix I posted was to do a full scan of the collection, not just an update. This, I believe rebuilds the collection, and fixes the problem.
Marking the bug as Invalid will, I believe, hide the bug from searches (it does this in bugs.kde.org), so marking it fixed would be better for other users who experience this problem.

I had the same problem now again in Hardy. A rescan (Tools->Rescan Collection) seemed to do the trick again. So what ever is causing this hasn't gone away yet.

I think it is a problem with Amarok, upsteam issue... They probably change something with the database version that needs a re-scan. It is not really an issue, as long as this bug is available for searching.

I wonder if the package could be scripted to rescan on install of the package: amarokcollectionscanner might do it?

I had the same problem with Hardy - and Rescan Collection fixed it.