[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amarok-bugs-dist
Subject:    [amarok] [Bug 327891] Pulsating current track indication is CPU intensive
From:       Freddie Chopin <freddie_chopin () op ! pl>
Date:       2015-05-15 17:07:01
Message-ID: bug-327891-71684-ujNnFtKg48 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=327891

--- Comment #34 from Freddie Chopin <freddie_chopin@op.pl> ---
I've just removed amarok stable version, removed all configs (everything with
*amarok* in name) that I could find in my home folder, compiled git version
(package amarok-git from Arch's AUR, amarok-git-v2.8.0.468.g014a851-1) and the
problem seems to be a bit smaller... With window minimized I get 5-10% on each
CPU, with window visible it's ~10%. The funny thing is that I now removed the
git version, removed the same config files and installed the stable version
again... And the usage of CPU is identical to the git version (~5% with window
minimized, ~10% with window visible).

Anyway - the playlist is still to be blamed, because if I hide it (so current
track is not highlighted) the usage with visible window drops to ~5%. When
window is minimized, CPU usage doesn't change.

Instead of hiding the playlist the problem can be confirmed in the way
described above - create long playlist, scroll it to the position when
currently playing track is not visible - CPU usage drops - scroll it back to
see currently playing track - CPU usage rises.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Amarok-bugs-dist mailing list
Amarok-bugs-dist@kde.org
https://mail.kde.org/mailman/listinfo/amarok-bugs-dist

[prev in list] [next in list] [prev in thread] [next in thread]