Bug 787448 - Spice 0.10 client overuses sound and heats up laptop to thermal shutdown
Spice 0.10 client overuses sound and heats up laptop to thermal shutdown
Product: Fedora
Classification: Fedora
Component: spice (Show other bugs)
i386 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Hans de Goede
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-02-05 02:23 EST by gvenkat
Modified: 2013-02-13 09:29 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 09:29:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description gvenkat 2012-02-05 02:23:38 EST
Description of problem:
Updating from spice 0.9 to spice 0.10 has created a problem with laptop leading to a thermal shutdown

Version-Release number of selected component (if applicable):
spice 0.10 client and server

How reproducible:
Run spice client on laptop. Use powertop to monitor wakeups. alsa-sink will be one of the highest reasons for wakeups that drains battery, heats up wireless card to the point the laptop shuts down with thermal alarm. Killing spice-client reduces the heat considerably. Muting the WIndows guest audio makes no difference to client alsa usage.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
spice 0.10 has made use of spice unusable on laptops by creating too many wakeups and overheating wireless card. This is noticeably different from 0.9 which had no such problems.

Suggestions: provide an option in spice to disable audio at the client side when not needed and save bandwidth as well.

Please Do regression testing between 0.10 and 0.9 for increased CPU usage and WiFi usage.
Comment 1 Adam Williamson 2012-05-09 12:24:19 EDT
I noticed this too, actually, in testing an F17 guest on my laptop (F16 host). Playing sound seemed to spin the fan up a lot.

Fedora Bugzappers volunteer triage team
Comment 2 Fedora Admin XMLRPC Client 2012-10-15 02:12:58 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Hans de Goede 2012-10-15 02:26:00 EDT

Are you still seeing this?

And which spice-client are you using? Please note that spicec has been deprecated. If you're still using spicec please give remote-viewer a try, as that is our preferred client now.


Comment 4 Fedora End Of Life 2013-01-16 08:38:09 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Fedora End Of Life 2013-02-13 09:29:45 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.