Log files requested to debug no audio from microphone/speaker on Chrome for Mac
hu...@webrtc.org
There is a long standing audio bug on Chrome for Mac where input (mic) or output (speaker) audio is missing, and nothing gets the audio back other than restarting Chrome or the coreaudio daemon (i.e. by killing it). In order to analyse this issue further we need debug data from users who encounter this issue.
If you run into this case, it would be great if you could do the following:
Make sure that nothing gets the audio back as long as Chrome is running
This is to verify that you’re likely running into this particular bug. Try the following as applicable and possible. If audio starts working, the problem you’re having is not this bug, no need to proceed and collect this data.
Keep the browser open. Don’t close it!
Check that the mic and speaker aren’t muted and properly connected. Test with another application (i.e. not Chrome) and verify that it works.
Try switching audio devices (input, output) in the web application you’re using. If the web application doesn’t support switching devices, test with this WebRTC sample.
Try restarting the web application. For a WebRTC call: hang up, reload the page, start a new call.
Test with AppRTC in loopback.
Sample the CoreAudio process
Open Activity Monitor (Command + Space, type “activity”).
In View menu, select “All processes”.
Search for “coreaudiod” (upper right).
Mark it and select “Sample Process” using the "wheel icon" menu (upper left).
Click “Save...” (upper right), provide file in the bug or share privately.
Sample Chrome’s browser process
Find the Chrome process id:
In the Chrome menu (three vertical dots in upper right corner), More tools > Task Manager.
Note the Process ID of the “Browser” task.
Open Activity Monitor (Command + Space, type “activity”).
In View menu, select “All processes”.
Search for “chrome” (upper right).
Mark the process with id as noted in step 1 and select “Sample Process” using the "wheel icon" menu (upper left).
Click “Save...” (upper right), provide file in the bug or share privately.
Make a system diagnose dump
The audio bug may need further investigation by Apple. If this is the case, a system diagnose dump from the moment when the bug happened is necessary. The generated file is large and may contain personal information, therefore do not attach it to a Chromium or WebRTC bug but keep it on your local machine. If the file is necessary for further analysis, we will ask you in the bug report. To generate the diagnose dump:
Press Shift+Ctrl+Option+Command+. (period)
Wait while data is collected. This can take up to a few minutes.
When done, a tmp folder (/private/var/tmp/) will appear with the latest sysdiagnose file selected.
Move the file to a folder where you can find it back, for instance in the Documents folder. Do not attach it to the bug report.
Crash Chrome
When Chrome crashes, valuable debug data is saved that may help to analyse the audio bug. Ensure you have no unsaved data in your open browser tabs, then force Chrome to crash by:
Go to Settings, show advanced settings, enable “Automatically send usage statistics and crash reports to Google”.
Copy and paste chrome://inducebrowsercrashforrealz in the address field and press return. Browser will crash.
Start browser again.
Go to chrome://crashes, verify that the crash is on top of the list (check timestamp), click “Send Now” to upload the crash dump.
When uploaded, provide the Uploaded Crash Report ID in the bug report.
Additional information
Please also provide the following information in the bug report:
Which direction of audio was missing? Input/mic (others can’t hear you), output/speaker (you can’t hear others), or both.
The audio device(s) used when the problem appeared.
Operating system and version.
Chrome version (chrome://settings/help)