Chrome Hangs if coreaudiod is not responding
Reported by
kmbarag...@gmail.com,
Sep 15 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. sudo killall -v -STOP coreaudiod 2. Notice that chrome has now become completely unresponsive, and may never wake up. 3. sudo killall -v -CONT coreaudiod 4. Notice that chrome responds again What is the expected behavior? It seems like better behavior if the application can continue in the face of audio daemon errors. What went wrong? Chrome is completely unresponsive during the period that coreaudiod is not responding. Did this work before? No Chrome version: 52.0.2743.116 Channel: n/a OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 22.0 r0 These sorts of errors really happen, particularly on sleep/wake cycles. May be tangentially related to 160920, but I don't see any mention of hanging there, only lack of audio.
,
Nov 30 2016
,
Feb 12 2018
,
Feb 12 2018
,
Feb 13 2018
The big question I think is: what would we do in this case? It's unfortunate that we seem to have to run CoreAudio calls on the main thread. The Audio Process work done by olka@ and team (hello!) should ensure Chrome in general doesn't hang in cases like these. Before that, I don't see it worth pursuing. If we're able to detect such hangs, what ought the user-facing result be? Just no audio? A message about coreaudiod having stoppped working and a request to restart it or the whole machine?
,
Feb 15 2018
,
Feb 15 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ccameron@chromium.org
, Sep 16 2016