Hangouts Chrome extension always reports audio activity; system can't sleep |
|||
Issue descriptionChrome Version: 66.0.3329.0 canary OS: Chrome 10352.0.0 (Official Build) canary-channel scarlet What steps will reproduce the problem? (1) Log in (2) Install Hangouts Chrome extension: https://chrome.google.com/webstore/detail/google-hangouts/nckgahadagoaajjgafhacjanaoiihapd?hl=en (3) Wait a few minutes What is the expected result? System will suspend automatically What happens instead? System stays awake indefinitely, with powerd claiming "Audio activity ongoing" Feedback report: https://listnr.corp.google.com/report/84997811969 chrome://media-internals says I have 1 stream open: Stream 0:1 channel_layout: MONO channels: 1 component_id: 1 component_type: 2 device_id: device_type: pcm_low_latency effects: NO_EFFECTS frames_per_buffer: 1024 owner_id: 0 sample_rate: 48000 status: started volume: 1 At some point it was blaming the Hangouts extension:// in the "Output controller" list, so I tried messing with Hangouts. From email: "I tried disabling-Hangouts/logging-out/logging-in, with no luck. But I think disabling/rebooting/logging-in worked." Potentially related: issue 799727 and issue 753596 Definitely not working well on M66. Not sure if it's a regression there, an existing issue, or something unique to Hangouts.
,
Jan 31 2018
I am not sure how hangout uses AudioContext, but it is the first step using audio. Whenever an AudioContext element is created, there will be an empty stream. I just checked again. By typing a = new AudioContext() in chrome developer console, there will be an empty stream which lasts for 30 seconds. But the point is, javascript developers can write whatever they want. There might be all kinds of scenarios where web app / android app use a dummy stream (maybe for better latency), so we need CRAS to detect such dummy stream, and let power manager know it can sleep.
,
Feb 2 2018
,
Apr 7 2018
Now that issue 753596 is closed, it'd be good to see if this is still an issue.
,
Apr 9 2018
I'm not sure I can reproduce this any more. In fact, I think the problem went away within a few days of my original report. Perhaps it was a temporary bug with the extension? To my knowledge, this would be 'WontFix' (cannot repro). Feel free to reopen if anyone thinks differently. |
|||
►
Sign in to add a comment |
|||
Comment 1 by louiscollard@chromium.org
, Jan 31 2018