After a fresh amarok install: If you just close the context view (and therefore the analyzer with it) the analyzer somehow runs in the back using precious cpu-ressources even if amarok is completely idle and minimized. (In my case with a 4GH CPU it is 2%) ... Imagine how many people use it ... and how this sums up over time. Not good for mother Earth. Workaround: Close the analyzer first, then close the context view. Please change this! And many thanks for the wonderful player!
Not a bug, and something you can change easily. Amaroks Context View is a feature, not a bug.
I think you misunderstood me. Of course is the Context View a feature! The bug is the following: If you close Context View ... the analyzer is still running.
Right, changing description of the bug, then, as the initial one is not really clear.
Thank you for reopening the bug! And thank you for improving the description of the bug! It's clearer now. Now one question remains for me: Now that we agree, that the Analyzer should be disabled when the Context View is disabled .... shouldn't the Analyzer also pause, when Amarok is idle and minimized? Why waste precious resources in this case? Should I open an additional bug report for this?