Hello!
I am writing about a problem I\'ve noticed with my first experience with amaroK. I compiled svn20060121 and everything was ok.
amaroK starts with ~40MB RAM consumption; after creating and populating playlist it grows to a 50 then while playing mp3/ogg it takes more and more memory with every song! Something about a 1MB for each song. After some time of playing you can found that it uses up to 300MBytes.
I can\'t say I am limited in memory, but WHY this happens? Is this normal? My Beep-media-player uses 16MBytes at startup and 22 (!) while playing for hours...
amaroK is very nice and sweet piece of software but this *leak* is just annoying. I wonder if there\'s anyone who pays attention to this high memory usage, or everybody think that `modern software can use tons of memory unless it is embedded\'

Are you using dynamic mode with user-created smart playlists?

If so, checkout again and re-save your smart playlists. If not, no idea

Hi - I've just encountered this, too.

It's happened twice, both times with amaroK eating more and more memory until my system is thrashing.  amaroK eventually crashed after the first time (which is how I figured out it was responsible, as my PC was too unresponsive to find out while it was going on).

The second time I realised what was happening and quickly made some temporary swap files to hold the excess - by the time I eventually killed the process it was using nearly 2Gb of memory.  Now correct me if I'm wrong, but surely that's not normal?

it's not normal. Do you have moodbar enabled at all? I've noticed that very occasionally, if exscalibar has trouble calculating the mood for a track, it will go into a tailspin and take RAM with it.

dangle_wtf wrote:it's not normal.

Didn't think it was

I don't think I have a moodbar - is it one of these things where if you don't know what it is, chances are you don't have it?

The second incident occurred while I was syncing my iPod...  No end to the problems with that thing, eh?
As soon as I fix one thing, something else pops up...

Pretty much, moodbar requires +exscalibar, so that's not your prob.

When you upgraded amaroK, did you start with a clean database, or your existing (I assume) mysql db?

It could be worth running mysqlrepair on your db in case it's been mangled by the ipod crashes - but that shouldn't cause RAM blowout.

Otherwise, turn on the debug USE flag, add FEATURES="nostrip" to your amaroK emerge and rebuild it.
Running amarok from a console should give more clue as to what might be happening.

Yup, you're right.  amaroK is -exscalibar, and I do use MySQL.

"mysqlrepair amarok -p" gave a list of all the amaroK tables with "OK" next to them.

I'm now rebuilding with debug and nostrip.  amaroK runs automatically when I log in, though - is there a log file for the KDE autostarter that keeps a record of all app's output, or will I have to keep starting it manually until it starts leaking again?

you might be able to edit the amarok.desktop file to tell it to run in a console - never tried this though.