Comment 2 for bug 149382

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.