Bug 209085 - [Windows] Amarok nightly occupies 100% CPU during playing and uses a lot of RAM.
Summary: [Windows] Amarok nightly occupies 100% CPU during playing and uses a lot of RAM.
Status: RESOLVED UPSTREAM
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.3-GIT
Platform: unspecified Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-01 12:03 UTC by Diego
Modified: 2009-11-03 17:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Log since the start and to the closure of amarok trying to play a file. (132.79 KB, text/plain)
2009-10-01 12:06 UTC, Diego
Details
Screenshot of memory status before opening amarok (not for the first time however). (53.71 KB, image/png)
2009-10-01 12:07 UTC, Diego
Details
Screenshot of memory status with amarok opened before playing a song. (134.82 KB, image/png)
2009-10-01 12:08 UTC, Diego
Details
Screenshot of memory and CPU status with amarok opened while playing a song. (138.67 KB, image/png)
2009-10-01 12:10 UTC, Diego
Details
Screenshot of memory status with amarok opened after playing a song. (136.01 KB, image/png)
2009-10-01 12:11 UTC, Diego
Details
Screenshot of memory status after closing amarok. (87.03 KB, image/png)
2009-10-01 12:12 UTC, Diego
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Diego 2009-10-01 12:03:15 UTC
Version:           2.2-GIT (using 4.3.00 (KDE 4.3.0), MS Visual Studio 2008 SP1)
Compiler:          cl.exe
OS:                Microsoft Windows (i686) release 5.1 (XP Professional)

Amarok nightly 30/09/2009 and 01/10/2009 doesn't reproduce any sound and occupies 100% CPU and a lot of memory just after starting reproduction. The memory doesn't free up until you close amarok.

Screenshots and log incoming.
Comment 1 Diego 2009-10-01 12:06:19 UTC
Created attachment 37285 [details]
Log since the start and to the closure of amarok trying to play a file.
Comment 2 Diego 2009-10-01 12:07:18 UTC
Created attachment 37286 [details]
Screenshot of memory status before opening amarok (not for the first time however).
Comment 3 Diego 2009-10-01 12:08:52 UTC
Created attachment 37287 [details]
Screenshot of memory status with amarok opened before playing a song.
Comment 4 Diego 2009-10-01 12:10:26 UTC
Created attachment 37288 [details]
Screenshot of memory and CPU status with amarok opened while playing a song.
Comment 5 Diego 2009-10-01 12:11:20 UTC
Created attachment 37289 [details]
Screenshot of memory status with amarok opened after playing a song.
Comment 6 Diego 2009-10-01 12:12:17 UTC
Created attachment 37290 [details]
Screenshot of memory status after closing amarok.
Comment 7 Diego 2009-10-31 13:03:57 UTC
No progress in today's nightly build.
Comment 8 Diego 2009-10-31 14:32:16 UTC
Mmm... this is sort of fixed and sort of not.
I discovered that at the moment:
a) I cannot get Amarok to reproduce any audio in any way;
b) if I reproduce an mp3 the CPU goes 100% for a bunch of seconds (~10 secs) and then goes to normal usage;
c) if I reproduce an ogg with the latest DirectShow oggfilter from:
http://downloads.xiph.org/releases/oggdsf/oggcodecs_0.81.15562-win32.exe
then CPU always stays 100% and it occupies a lot of memory;
d) if I reproduce an ogg with the oggcodecs 0.9.9.5 package in the repo then Amarok crashes.

So, to sum up: the most of the problems are about ogg reproduction.
With the 0.9.9.5 codecs you get a crash; I think it's because they're old, this page lists 0.9.9.6 as 2004:
http://www.free-codecs.com/download/Ogg_DirectShow_Filters.htm
With the 12/2008 Xiph codecs:
http://www.free-codecs.com/download/Filters_for_Ogg_Vorbis_Speex_Theora_and_FLAC.htm
http://www.xiph.org/dshow/
You get 100% CPU usage and high memory consumption.

So, afterall probably this is not Amarok's fault. Mp3 first seconds 100% CPU usage somehow concerns me, that's why I won't close this report for now.

Some test with other Phonon backend maybe can shed some light on this kind of issues, so please help me in this thread if you can:
http://forum.kde.org/viewtopic.php?f=59&t=83285&p=135370#p135370

Thanks.
Comment 9 Diego 2009-11-03 17:15:33 UTC
As my suspects told me this is a Phonon-DirectStream problem only.
This isn't an Amarok problem, Phonon-VLC works like a charm (Phonon-Mplayer should too).
If any Windows user reports reproduction problems please advise them to try other Phonon backends.

Here's a temporary howto:
http://forum.kde.org/viewtopic.php?f=59&t=83285&p=135936#p135917