Amarok scan collection _really_ memory hungry?

[Rich]

On 2007.04.26. 11:57, Mark Kretschmann wrote:
...
>> So, I appear to have worked around it by starting again and leaving it
>> running overnight, but that hardly seems an easy solution.  Do people
>> want me to do some further investigation as to why it is happening and
>> if amarok can be changed? Or is it just a particularly degenerate case?
>> I don't think amarok should attempt to consume more than 4GB of swap at
>> worst - most users don't have that much swap + ram.
> 
> Well, this extreme memory usage is obviously not normal. It's probably choking 
> on a specific file.
> 
> When it starts to freak out, kill Amarok, and then look at the file 
> ~/.kde/share/apps/amarok/collection_scan.log. The file that's listed in there 
> is the last one that the scanner has processed - which is likely the culprit. 
> Remove it from your collection.

also, try opening file properties in konqueror and see "meta info" tab. 
if this process also is slow and uses a lot of ram, most probably 
problem is within taglib.

> --
> Mark
-- 
  Rich