After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 441385 - Rhythmbox keeps CPU awake even when paused
Rhythmbox keeps CPU awake even when paused
Status: RESOLVED DUPLICATE of bug 399012
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: Normal minor
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-26 10:02 UTC by Alexander Hunziker
Modified: 2007-05-26 10:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexander Hunziker 2007-05-26 10:02:51 UTC
Please describe the problem:
I just realised that my CPU doesn't go to power save states C3 and C4 when rhythmbox is running but paused. That means that somehow rhythmbox is keeping the CPU busy enough that it never finds the time to fall asleep. Is it constantly polling something?

In my case, the difference ist more than 1.5W, which is almost 10% of the overall power consumption.

I can't run Intel's PowerTop to observe it more precisely, because I don't have new enough a kernel. But "luckily" my Thinkpad has this bug that it emits a high pitched noise when the CPU is in C3 and C4, so I can actually hear it. Still, I can also observe the difference when I observe the discharge rate of the battery.

Steps to reproduce:
1. Start rhythmbox, play a song, pause it.
2. Observe power usage, for example using /proc/acpi/battery/...
3. Quit rhythmbox
4. Observer power usage again.


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Jonathan Matthew 2007-05-26 10:15:50 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

We've already done a fair bit of work on this.  It'll be much better in the next development version (0.11.0) which will be released soon.

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