I recently upgraded to amarok 1.4.4 (I'm running Debian Unstable), now I can't build the collection.
I have about 90 gigs of mp3s that I need to scan through. When build the collection, amarok uses more and more RAM, and eventually, at about 70%, I'm out of RAM.
Which leads to amarok dying, it just stops.

I tried removing collection.db and amarokrc, but it didn't get better.
'amarok -version' gives me:
Qt: 3.3.7
KDE: 3.5.5
Amarok: 1.4.4

What can I do to fix this situation?

Sort of the same deal here-

My top reads:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
28488 seiferth  25  0 84668  56m  13m R  100  5.6 270:05.02 amarokcollectio

the collection_scan.log tail reads:
/home/RAID/musicshare/Pink Floyd/1967 - The first three singles/01 - arnold layne.mp3seiferth@acoma:~/.kde

This same set of files is built on a FC5 system running 1.4.4 both using SQL lite and the same set of files (on a Samba exported file share).

I may go to using mysql and a shared database if I can't get this to work. I would be glad to provide whatever logs, etc are needed. Amarok's collection building appears to be the most troublesome (from an end user point of view) part of the system. Basically it seems Amarok is a no go on Edgy at the moment at least for some (large) libraries.

I suggest you two both have a look through some of the older posts on the forum for some suggestions as to what he problem might be.

I spent about an hour searching the forums before creating my post, and I really couldn't find any suggestions on how to fix anything related to this except for removing collection.db and amarokrc.
If you could point me to a relevant thread I'd be a happy camper.