Start the browser with parameters and generate logs

For Mac start Chrome:

method one :

1. Quit all running instances of Chrome.
2. Run the terminal application.
3. In a terminal, run the following command:
4. /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-logging=stderr --v=1 > log.txt 2>&1
5. Press  Enter  .
6. In which directory the above command is executed, a log file should be generated there: log.txt

Method Two:

Start command: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-logging --v=1

Check the log at: /Users/yumlu/Library/Application\ Support/Google/Chrome/ chrome_debug.log 

In addition, if you add the force- fieldtrials parameter, such as:

Start command: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-logging --v=1  --force-fieldtrials="WebRTC-SpsPpsIdrIsH264Keyframe/Enabled/"

For Mac start Firefox: 

/Applications/Firefox.app/Contents/MacOS/firefox --enable-logging --v=1

For Windows start Chrome:

1.   Launch chrome (assume chrome installation directory is C:\Program Files\Google\Chrome\Application\chrome.exe)

"C:\Program Files\Google\Chrome\Application\chrome.exe" --enable-logging --v=1, --no-sandbox

2.   WebRTC related logs would be generated in User Data Directory which named chrome_debug.log

%LOCALAPPDATA%\Google\Chrome\User Data\chrome_debug.log

如：C:\Users\luyum\AppData\Local\Google\Chrome\User Data\chrome_debug.log

extension:

The parameters for disable WebRTC encryption are:

 --args --test-type  --disable-webrtc-encryption

The official version of the browser should not have this parameter, you can use Chrome Canary or your own built Chromium