My amarok 2.5.0 is configured with a dynamic playlist. After every song I can see an increment in amaroks memory usage (visible in KDE System Activity and top etc.) Today amarok made my desktop nearly unusable because it eated up all my 4GB of RAM and 2GB of swap (which shouldn't barely be touched at all in normal business) ;-( Reproducible: Always Steps to Reproduce: 1. Start a dynamic palylist feed (display 20 upcoming songs in advance, maybe thats important?) 2. Listen to your local collection for a few hours :) No, RAM increases immediately after the second song. Every song eats a few mega bytes after it is palyed (or the new upcoming song?)... 3. Kill amarok when it reserved 99% of RAM for itself :) Actual Results: Amarok is hungry... very hungry. Expected Results: RAM consumption should be nearly static. Maybe the source of the problem depends on some other special settings in my amarok. I hope you can reproduce this memory leak. I can give more information if you need.
Could you please disable all external scripts to eliminate any other error sources. Does this also happen without a dynamic playlist? Make sure you have all debugging symbols installed fro amarok and its dependencies (mainly phonon and phonon-backend-gstreamer or -vlc, depending on which you use). Then please run amarok for a few minutes (3-4 song changes) with this command from a konsole: valgrind --tool=memcheck --leak-check=full --track-origins=yes -v amarok and attach the output to this report. This will cause amarok to be very slow on start, but the playback should work as usual.
Created attachment 70610 [details] Output from valgrind Here you go. See the attachment. I deactivated all scrips. I played 3-4 songs and quit amarok with Ctrl-Q afterwards. I hope there is some useful information in it...
Additional information: Dynamic playlist or not. I can count a significant memory inceasing of about 800 KB after every song.
Comment on attachment 70610 [details] Output from valgrind Sadly your valgrind output is aborted and lacks the summary. Did you quite Amarok with Ctrl+Q?
I tried it again, the same output, no summary. And yes, I did quit Amarok mit Ctrl-Q and waited until the bash was ready again... My command was: valgrind --tool=memcheck --leak-check=full --log-file=amarok.valgrind.out --track-origins=yes -v amarok --debug
Thank you for the feedback.
not reproducible with amarok 2.6
(In reply to comment #7) > not reproducible with amarok 2.6 How long did you let it run? IIRC this is a known bug with the gstreamer backend, that I can't reproduce with the vlc backend, so maybe this is fixed now. Depends on the version of the gstreamer backend I presume. Andreas: could you please test with Amarok 2.6 and the vlc backend as well?
Closing for lack of feedback. Please feel free to reopen if you can reproduce this with Amarok 2.6.90 aka 2.7 beta1 or Amarok 2.7, to be released in a few days.
Amarok 2.8.0 It was turned on about 2 days, eats 2.1 GB of memory
(In reply to user11 from comment #10) > Amarok 2.8.0 > > It was turned on about 2 days, eats 2.1 GB of memory This bug was closed in 2013 and was about a completely different version. FWIW: the problem was the phonon backend, not Amarok, and should be fixed with a newer version of that phonon backend since quite some time. Not reproducible here with the gstreamer backend and Amarok from git master which is ahead by several hundred commits of version 2.8. You should maybe try with amarok 2.9. beta, aka 2.8.90