New issue
Advanced search Search tips

Issue 648316 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue webrtc:4799
Owner: ----
Closed: Sep 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Mic is not taking any audio (others cannot hear)

Reported by chiraggu...@gmail.com, Sep 19 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36

Example URL:
https://test.webrtc.org/

Steps to reproduce the problem:
1. Keep your Chrome browser open for couple of days and use WebRTC calls may be 1-5 a day.
2. Number of days are not certain but within few days say 3-5 you should not be able to get Mic. Meaning others cannot hear you
3. Shutting down the browser and restarting resolves the issue.

What is the expected behavior?
Expected behavior is that browser can be running for days, weeks, or even months webRTC should work.

What went wrong?
Others cannot hear you. This is very fundamental

Did this work before? N/A 

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes 

Chrome version: 53.0.2785.116  Channel: stable
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 23.0 r0

This is a major issue and MUST be resolved quickly since there is no error when trying to capture the Mic.
 
webrtc_internals_dump (11).txt
300 KB View Download
webrtc_internals_dump (10).txt
277 KB View Download
webrtc_internals_dump (9).txt
244 KB View Download
webrtc_internals_dump (8).txt
211 KB View Download
webrtc_internals_dump (7).txt
141 KB View Download

Comment 1 by rsesek@chromium.org, Sep 19 2016

Components: -Internals>Media Blink>WebRTC>Audio
BTW Firefox doesn't have this issue. Mic is available to capture audio.

This issue is specific to Chrome.

Would really appreciate to be fixed ASAP.
There is no easy/quick fix for this issue. Details can be found in https://bugs.chromium.org/p/webrtc/issues/detail?id=4799 where a proposal on how to detect the problem also is presented.

We are working on a more long-term solution to move the audio parts to a separate process since that will avoid the problem where OS X does not deliver recorded audio after being paused for a very long time.

Restarting Chrome or Core Audio are other options. See e.g. http://superuser.com/questions/647396/reload-mac-audio-drivers-without-rebooting
Mergedinto: webrtc:4799
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment