trouble with amarok while scanning collection [SOLVED]

[Clansman]

Hi,

I've been having this annoying problem since a few versions back of amarok.

I'm now running amarok 1.4.3 (kde 3.5.4) and everytime I need a collection rescan (for whatever reason), it quickly takes up all my memory and then starts eating away all the swap it can. After a long time of constant swapping, one of two things happen:
- the collection get's rescanned and eventually not many applications were killed by the kernel's OOM killer;
- the collection scan processes die by the OOM hand.

I've tried switching back to sqlite (I've been using the collection on a mysql database ever since amarok implemented that) but there isn't any change. The database engine runs fine (rails and other web apps) and there is nothing wrong with the rest of the system.

Am I the only one having this issue? Is there a known way to fix it? What could be the problem?

Thanks everyone,
_________________
http://www.pjvenda.org

[markey]

Could be you have m4a/mp4 files in your collection? IIRC there were some memory leak issues with these files (fixed in SVN). Try to move them away.
_________________
Mark Kretschmann -- Amarok developer

[Clansman]

[Clansman]

Hi markey,

I got rid of all m4a files and amarok behaved normally this time.
Goes back into the "perfect" category

Thanks for the tip.

[]
_________________
http://www.pjvenda.org