My guess:
On the first run, it scans all the music in the dir you have pointed out to contain music.
This music is indexed. The indexed music is filled into a database.
I guess this is causing the CPU to run at 100%.
If you can connect to the adminpage with your browser, and see the scanner on Idle, then it is something else…