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 512617 - Playing internet radio uses a lot of processor power
Playing internet radio uses a lot of processor power
Status: RESOLVED DUPLICATE of bug 385061
Product: rhythmbox
Classification: Other
Component: Internet Radio
0.11.x
Other All
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-28 17:32 UTC by Milosz Tanski
Modified: 2008-01-28 22:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milosz Tanski 2008-01-28 17:32:39 UTC
Please describe the problem:
I noticed that when listening to an internet radio station rhythmbox uses a lot or processor power to do so. If I add the cpufreq applet to the panel, I constantly see the processor at the higest possible speed a large portion of the time. According to top rhtymbox uses between 25-30% of the cpu.

Steps to reproduce:

1. Add internet radio to rhythmbox, in my case npr: http://umtv-live.rs.itd.umich.edu/wuom/miradio32k.m3u
2. Play internet radio.
3. Obseserve rhythmbox use 25% of the cpu and eat your laptop battery away.
4. Pause rhythmbox, watch rhythmbox use 0% cpu.
5. Play a regular mp3 file... watch rhythmbox use < 10% cpu power.
6. Play internet radio again... watch the cpu spike again.


Actual results:
My laptop battery hates me.

Expected results:
After listening to internet radio for about 2 hours... cpu time on rhythmbox is about 35 minutes.

Does this happen every time?
Yes.

Other information:
I'm using Ubuntu gutsy and rhythmbox is using the gstreamer pulse audio backend.
Comment 1 Jonathan Matthew 2008-01-28 22:27:17 UTC
Most of the CPU time is being spent in GStreamer's audio resampler.

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.


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