Bug 288876

Summary:	Amarok consumes a lot of memory/RAM on first startup for the user (and at other times).
Product:	[Applications] amarok	Reporter:	Shlomi Fish <shlomif>
Component:	general	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version:	2.4.90 (2.5 beta)
Target Milestone:	2.6
Platform:	Mageia RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screenshot of htop after Amarok consumes a lot of RAM.

Description Shlomi Fish 2011-12-13 09:40:07 UTC

Version:           2.4.90 (2.5 beta) (using KDE 4.7.3) 
OS:                Linux

In a new UNIX user account, after starting Amarok from the "K" menu, it consumes over 12% of my 3 GB of RAM / memory (I'm on an x86-64 laptop running Mageia Linux Cauldron). It also happen in my existing user under certain circumstances.

Reproducible: Always

Steps to Reproduce:
1. Create a new UNIX user.

2. Start Amarok from the K Menu.

3. Select "United States" as the Amazon Store.

4. Keep the next dialog box saying whether to scan the ~/Music folder hanging.

5. Start a konsole terminal with "htop" or "top".

Actual Results:  
Amarok consumes a lot of RAM.

Expected Results:  
Amarok should not consume so much RAM.

It seems better after the second invocation for the same user, but the same large memory consumption happens in my populated user sometimes as well.

Comment 1 Myriam Schweingruber 2011-12-14 07:10:26 UTC

12% of RAM, do you mean residual memory? Please give the line from htop or top

Comment 2 Shlomi Fish 2011-12-14 07:43:55 UTC

Created attachment 66724 [details]
Screenshot of htop after Amarok consumes a lot of RAM.

This is a screenshot of htop after Amarok consumes a lot of RAM at startup in a new user.

Comment 3 Shlomi Fish 2011-12-14 07:46:42 UTC

(In reply to comment #1)
> 12% of RAM, do you mean residual memory? Please give the line from htop or top

I mean Random-access-memory, not swap. That's what htop/top reports there. See the screenshot I attached.

Comment 4 Myriam Schweingruber 2011-12-14 08:11:53 UTC

Well, there is the virtual memory but it is the residual memory use that matters. Yours us just 371M which is absolutely correct.
FWIW: I suggest you read up some documentation on dynamic memory use in Linux. In short: the more memory available, the more will be used, the system distributes this evenly to the running processes depending on their priority.

Not a bug.