Issue metadata
Sign in to add a comment
|
Chrome stops receiving audio input after update until restarted |
||||||||||||||||||||||||
Issue descriptionChrome Version : Seems version independent, this is ongoing issue that has been happening for months. OS version : 10.11.6, but has been present from at least 10.11.5 Behavior in Safari (if applicable): Behavior in Firefox (if applicable): What steps will reproduce the problem? (1) Wait for Chrome to have updated, without restarting chrome (2) Join hangouts video call (or any Chrome app/website that uses microphone) (3) Try to speak What is the expected result? Microphone works What happens instead? Microphone does not work (no audio received in Chrome) I have seen this bug a lot in Techstop (usually a few walkups per day in one of our offices, for months now). Issue seems to appear after Chrome updates in the background, after which you will have to restart Chrome to fix issue. Issue does not affect all users, and only affects users on Mac OS. It affects both internal and external microphone, but microphone is still working when checking Microphone settings. It is only Chrome that fails to receive audio. Considering how long going this issue is, I am sure there is an open bug already this can be merged to. What data/logs etc. do you want collected next time it happens?
,
Dec 14 2016
Unable to reproduce this issue on Mac 10.12.1. 1. Installed chrome dev version 56.0.2924.18 and updated to 57.0.2946.0 2. Without restarting the chrome, joined the hangouts video call. Observed that i was able speak successfully in the video call. Could you please try this scenario with clean profile with out using any apps and extensions and let us know your observations.
,
Jan 13 2017
Hello stefanvirtanen@, It would be great to get system.log output from the Console app, around the time of the update/audio failure. Also we need to know the version of Chrome having the problem.
,
Jan 16 2017
Hello shrike@ This has AFAIK been an issue in Chrome on stable for almost 12 months. The 'if update is pending' is an educated guess (I work in support, it is common for users to come in with audio input having stopped working on OS X, they will generally have a pending update in Chrome. Restarting chrome fixes it) I'll try to remember to pull the system.log output the next few times
,
Jan 23 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 24 2017
,
Mar 13 2017
Cleaning up sheriffbot label "Needs-Review" label as a part of modified "Needs-Feedback" sheriffbot rule. [ref bug for cleanup 684919]
,
Oct 30 2017
Probably a dupe of issue 160920?
,
Oct 30 2017
,
Oct 31 2017
I'm not sure if we ever looked specifically into "no audio after Chrome update": in Issue 160920 we consider system sleep/resume as a triggering condition. ossu@ - probably you want to take a look and track it separately?
,
Oct 31 2017
It's quite possible this is unrelated to the actual Chrome update being downloaded, though. From comment #5, I get the feeling this may just be very long-running Chrome instances, since they have a pending update. There might be something else at play than in 160920, but without more information, I think we should wait and see if the hotfix experiment pans out and this problem starts disappearing.
,
Oct 31 2017
It might simply be that those with long uptimes will also usually have an update pending because of that. Techstop could probably encourage users to make sure they are using the latest version of Chrome (including restarting) before requesting further support (and for "no audio" issues specifically, try restarting Chrome even if there's no update pending). |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Dec 1 2016Labels: M-57