New issue
Advanced search Search tips

Issue 674737 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression

Blocked on:
issue chrome-os-partner:60497



Sign in to add a comment

cras and powerd start chewing CPU on resume from sleep

Project Member Reported by w...@chromium.org, Dec 15 2016

Issue description

Chrome Version: 57.0.2951.0 dev (64-bit)
OS: ChromeOS Panther

What steps will reproduce the problem?
Not sure; I happen to have Google Play Music open in a tab (paused at the time I let the device sleep) and a Chrome Remote Desktop session to a Windows box (which remotes audio).
(1) Allow ChromeOS device to sleep.
(2) Wake ChromeOS device and unlock.

What is the expected result?

Expect that device resumes and operates normally.

What happens instead?

Device is very janky (e.g. text typed into a tab takes several seconds to appear) and top shows cras and powerd processes, and sometimes rsyslogd or kswapd, consuming a lot of CPU.
 

Comment 1 by w...@chromium.org, Dec 15 2016

Was just able to repro this without Chrome Remote Desktop running, only Google Play Music.

Comment 2 by w...@chromium.org, Dec 15 2016

Issue appears to trigger if I do something I/O intensive, e.g. open chrome://system while audio is playing.

Comment 3 by dgreid@chromium.org, Dec 15 2016

how much is "a lot"?

Can you link a feedback report?  That will have a reason for both powerd and cras wakeups.

Thanks!

Comment 4 by w...@chromium.org, Dec 15 2016

Re #3: Yup, I have already filed a feedback report, including this bug # in the description text.

Re "a lot", the CPU usage was 80%+, and sufficient to make the mouse cursor stop moving at times, and to cause text to take several seconds to enter.

Comment 5 by dgreid@chromium.org, Dec 15 2016

Owner: cychiang@chromium.org
Status: Assigned (was: Untriaged)
syslog filled with recover device and metrics failures?  Will the recent changes to fix the device resetting fix this too?
Blockedon: chrome-os-partner:60497
Thanks for the feedback!

Yes this will be fixed by https://code.google.com/p/chrome-os-
partner/issues/detail?id=60497.

Make this blocked by https://code.google.com/p/chrome-os-partner/issues/detail?id=60497 so we can verify after the fix get merged.

Comment 7 by w...@chromium.org, Jan 6 2017

Status: Fixed (was: Assigned)
Issue no longer repros in 57.0.2970.0 dev.
Status: Verified (was: Fixed)
verfied in Chrome OS 9202.0.0, 57.0.2984.0. 

Sign in to add a comment