I just installed amarok 1.4 on ubuntu dapper (I use gnome but I have KDE installed as well). as it is scanning my music directory, it starts eating more and more  ram and swap memory until it just stops responding to input. I have about 130gb of music, and it crashes at about the 80% mark straight after boot. I have 1gb of ram and a 512mb swap partition (just so you guys can get an approximation of how long it takes to crash). I hope there'll be a fix for this soon.. I used 1.3 for a while on Breezy with absolutely no problems to speak of but then upgraded to 1.4 when I upgraded to Dapper.

Does it crash at the same place each time you try building your collection? Check the log files in ~/.kde/share/apps/amarok/ to see the last file successfully processed.
As another test, on the command line, as the same user you're running amarok as, try:

Code: Select all

amarokcollectionscanner --recursive

This goes through the same process as the internal scanner, but outputs to the screen rather than the database. If this **** out, try moving the file it was trying to read out of your collection, and run it again.

Next, try backing up/deleting ~/.kde/share/config/amarokrc and starting amarok again.

You can also try building a completely new database. Backup/delete ~/.kde/share/apps/amarok/ dir and ~/.kde/share/config/amarokrc

Also, try setting your swap to the same size as your real RAM. This can help for some.

well, I just ran it again, and the results are interesting.. the ram usage stays constant until it gets to 80% scanned, at which point it stops scanning and proceeds to eat away my ram and a fairly fast rate (~50mb/s I'd say). I tried doing a killall amarok before it crashed but for whatever reason it said that amarok wasn't running.

and the command you gave me doesn't work.. it says command not found.

what about the other stuff?

I gave you several alternatives there.

Also, see this thread:

http://amarok.kde.org/forum/index.php/t ... l#msg12688