Bug 344194 - active track widget glow animation causes high cpu usage
Summary: active track widget glow animation causes high cpu usage
Status: RESOLVED DUPLICATE of bug 327891
Alias: None
Product: amarok
Classification: Applications
Component: Playlist (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR normal
Target Milestone: 2.9
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-15 15:32 UTC by dmr drk
Modified: 2015-04-15 22:09 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dmr drk 2015-02-15 15:32:09 UTC
active track widget glow animation uses cpu three times higher than normal, if minimize amarok or disable animation before compile time, usage back to normal. Same usage with clementine but user can disable it.

Reproducible: Always
Comment 1 Myriam Schweingruber 2015-02-16 05:49:40 UTC
Are you talking about Amarok 2.8 or current git? Please always specify the exact Amarok version you are working with
Comment 2 dmr drk 2015-02-21 22:29:04 UTC
(In reply to Myriam Schweingruber from comment #1)
> Are you talking about Amarok 2.8 or current git? Please always specify the
> exact Amarok version you are working with.
2.8 and higher.
Comment 3 Myriam Schweingruber 2015-02-22 02:36:25 UTC
Could you please be precise what exact version you reproduce this bug with? 2.8 and higher is nebulous at its best. if you use current git, then please specify the output of git describe
Comment 4 dmr drk 2015-03-03 19:31:56 UTC
(In reply to Myriam Schweingruber from comment #3)
> Could you please be precise what exact version you reproduce this bug with?
> 2.8 and higher is nebulous at its best. if you use current git, then please
> specify the output of git describe
higher: same cpu usage since 2.8, this could not be amarok's bug but if amarok has enable-disable options, could be better performance for old computer. 
last one, ab52017, date:2015-02-03.
Comment 5 Myriam Schweingruber 2015-03-03 23:30:02 UTC
If you are using the git version, please run the command "git describe" this will give the exact version.
The latest version is v2.8.0-458-g53f0980, I don't know what "ab52017" stands for.

FWIW: I don't see any raise in the CPU usage with the latest git, maybe you are using a different desktop theme?
Comment 6 dmr drk 2015-04-15 21:32:20 UTC
(In reply to Myriam Schweingruber from comment #5)
> If you are using the git version, please run the command "git describe" this
> will give the exact version.
> The latest version is v2.8.0-458-g53f0980, I don't know what "ab52017"
> stands for.
> 
> FWIW: I don't see any raise in the CPU usage with the latest git, maybe you
> are using a different desktop theme?

"ab52017" is from quickgit.kde.org.
i tried with diffrent theme but nothing changed.
could those same bug ?
https://bugs.kde.org/show_bug.cgi?id=327891
https://bugs.kde.org/show_bug.cgi?id=244896
Comment 7 Myriam Schweingruber 2015-04-15 22:09:34 UTC
(In reply to dmr drk from comment #6)
> (In reply to Myriam Schweingruber from comment #5)
> > If you are using the git version, please run the command "git describe" this
> > will give the exact version.
> > The latest version is v2.8.0-458-g53f0980, I don't know what "ab52017"
> > stands for.
> > 
> > FWIW: I don't see any raise in the CPU usage with the latest git, maybe you
> > are using a different desktop theme?
> 
> "ab52017" is from quickgit.kde.org.

It doesn't help much, the best version number you can get is when you run "git describe".

> i tried with diffrent theme but nothing changed.
> could those same bug ?
> https://bugs.kde.org/show_bug.cgi?id=327891

Yes, that is indeed the same bug. I mark this one as a duplicate. I still can't reproduce this here at all, my CPU usage doesn't raise at all.

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

No, unrelated

*** This bug has been marked as a duplicate of bug 327891 ***