How to track logs from Chrome extensions.

If you're developing a Chrome Extension, creating bug reports with the full context can be hard, as logs and errors are hidden within background processes.

With Dashcam, you attach logs from Chrome Debug Mode to video bug reports and get the full context behind issues.

First, you'll need to run Chrome in debug mode.

Run Chrome in Debug Mode


  1. Quit any running instance of Chrome.

  2. Run the terminal application.

  3. In the terminal, run the command: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-logging --v=1

  4. Press Enter.


  1. Quit any running instance of Chrome.

  2. Right-click your Chrome shortcut.

  3. Select Properties.

  4. At the end of the Target: line, add the command line flags: --enable-logging --v=1 With that example flag, it should look like: chrome.exe --enable-logging --v=1

  5. Launch Chrome using your shortcut.

Verify Chrome Debug Logs

Verify that Chrome is now writing debug logs to a file. The file is called chrome_debug.log and will be found in the following location:


~/Library/Application Support/Google/Chrome/chrome_debug.log


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

Configure Dashcam to Monitor Chrome Debug Logs

Finally, configure Dashcam to monitor this file for changes.

  1. Navigate to the Logs configuration window

  2. Select System

  3. Supply the file path from the previous step

  4. Click Save

Your next Dashcam clip will include logs from Chrome debug mode, including the logs from your extension!

Note that Dashcam will only attach new logs, so be sure to launch your browser in debug mode to fully test.

Last updated