Can anybody confirm this behaviour?

At startup Amarok 2.1svn (at the moment revision 953083) takes about 80 MB of RAM, which I think is OK for my big music collection (~35000 files). But then Amarok constantly increases memory usage by about 1 MB every minute. Even if it does nothing (not playing, not scanning, ...).

After running it for a day it completely slows down my computer.

I can't confirm the 1-MB-per-minute behavior, but it certainly uses more memory than earlier versions did. My swap was rarely used at all before I upgraded Amarok to 2.1beta, but now it tends to be used quite a bit more (and for the record, I have 2 gigs of RAM in my machine). I'm only happy I went-over-the-top for my swap-partition or it's likely that even swap would have been exhausted.

And I've learned that I should never, under any circumstances, open up the cover-manager. That one eats memory as if it was going out of fashion (admittedly, it did that in both 2.0.x as well as 1.4 though although in the case of 1.4.x, not at all to the same extent).

There does seem to be some pretty serious memory-leaks somewhere.

thenktor wrote:Can anybody confirm this behaviour?

At startup Amarok 2.1svn (at the moment revision 953083) takes about 80 MB of RAM, which I think is OK for my big music collection (~35000 files). But then Amarok constantly increases memory usage by about 1 MB every minute. Even if it does nothing (not playing, not scanning, ...).

After running it for a day it completely slows down my computer.

Please try disabling "Watch Folders For Changes" in the collection config, and see if that makes a difference.

Mark Kretschmann wrote:Please try disabling "Watch Folders For Changes" in the collection config, and see if that makes a difference.

So far, it seems to do so. True, the time since the suggestion was given probably isn't enough to draw any definite conclusions but so far I have yet to run into the amarok-uses-20%-or-more-of-swap that I previously ran into after having it run for 4-5 hours.

Mark Kretschmann wrote:Please try disabling "Watch Folders For Changes" in the collection config, and see if that makes a difference.

This definitely helps. After leaving Amarok alone for about 4 hours without playing, the memory usage is still at ~100 MB. With this option enabled it would probably use ~400 MB memory now. So there has to be a bug which should be fixed before releasing version 2.1. Open a bug report for it?

thenktor wrote:

Mark Kretschmann wrote:Please try disabling "Watch Folders For Changes" in the collection config, and see if that makes a difference.

This definitely helps. After leaving Amarok alone for about 4 hours without playing, the memory usage is still at ~100 MB. With this option enabled it would probably use ~400 MB memory now. So there has to be a bug which should be fixed before releasing version 2.1. Open a bug report for it?

Yes, please open a bug report. I will look at it.

Bug report: http://bugs.kde.org/show_bug.cgi?id=189868