Chrome Canary Macos

| Posted on by



Jun 26, 2017 Web Scraping with Selenium and Headless Chrome on macOS. And with the headless browser option in Chrome 59+, you can use Selenium without having to open an actual Chrome window on your desktop. May 04, 2011 Google Chrome Canary was launched for Windows users in August 2010 and is a regularly updated and often unstable version of the browser where future features are tested out.

Getting Involved‎ > ‎

Download Chromium


You can test Chrome builds or Chromium builds. Chrome builds have the most infrastructure for analyzing crashes and reporting bugs. They also auto-update as new releases occur, which makes them a good choice for most uses. Chrome Canary is available for Windows and Mac and autoupdates daily. Other channels (dev and beta) are available.
Chromium builds do not auto-update, and do not have symbols. This makes them most useful for checking whether a claimed fix actually works. Use the following instructions to find builds:

Easy Point and Click for latest build:

Open up https://download-chromium.appspot.com

Easy Script to download and run latest Linux build:

Not-as-easy steps:

  1. Head to https://commondatastorage.googleapis.com/chromium-browser-snapshots/
  2. Choose your platform: Mac, Win, Linux, ChromiumOS
  3. Pick the Chromium build number you'd like to use
    1. The latest one is mentioned in the LAST_CHANGE file
  4. Download the zip file containing Chromium
  5. There is a binary executable within to run

Please file bugs as appropriate.


Downloading old builds of Chrome / Chromium

Let's say you want a build of Chrome 44 for debugging purposes. Google does not offer old builds as they do not have up-to-date security fixes.
However, you can get a build of Chromium 44.x which should mostly match the stable release.
  1. Look in https://googlechromereleases.blogspot.com/search/label/Stable%20updates for the last time '44.' was mentioned.
  2. Loop up that version history ('44.0.2403.157') in the Position Lookup
  3. In this case it returns a base position of '330231'. This is the commit of where the 44 release was branched, back in May 2015.*
  4. Open the continuous builds archive
  5. Click through on your platform (Linux/Mac/Win)
  6. Paste '330231' into the filter field at the top and wait for all the results to XHR in.
  7. Eventually I get a perfect hit: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/330231/
    1. Sometimes you may have to decrement the commit number until you find one.
  8. Download and run!
* As this build was made at 44 branch point, it does not have any commits merged in while in beta.
Typically that's OK, but if you need a true build of '44.0.2403.x' then you'll need to build Chromium from the 2403 branch. Some PortableApps/PortableChromium sites offer binaries like this, due to security concerns, the Chrome team does not recommend running them.

Contents

Chrome Canary Macos
  1. 5 Android
Chrome

There are command line flags (or 'switches') that Chromium (and Chrome) accept in order to enable particular features or modify otherwise default functionality.

Current switches may be found at http://peter.sh/examples/?/chromium-switches.html

It is important to note that some switches are intended for temporary cases and may break in the future.

Note that if you look at chrome://flags to see if the command line option is active, the state might not be accurately reflected. Check chrome://version for the complete command line used in the current instance.

Windows

  1. Exit any running-instance of Chrome.
  2. Right click on your 'Chrome' shortcut.
  3. Choose properties.
  4. At the end of your 'Target:' line add the command line flags. For example:
    • --disable-gpu-vsync
  5. With that example flag, it should look like below (replacing '--disable-gpu-vsync' with any other command line flags you want to use):
    chrome.exe --disable-gpu-vsync
  6. Launch Chrome like normal with the shortcut.

macOS

  1. Quit any running instance of Chrome.
  2. Run your favorite Terminal application.
  3. In the terminal, run commands like below (replacing '--remote-debugging-port=9222' with any other command line flags you want to use):
    /Applications/Chromium.app/Contents/MacOS/Chromium --remote-debugging-port=9222
    # For Google Chrome you'll need to escape spaces like so:
    /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --remote-debugging-port=9222

Linux

  1. Quit any running instance of Chrome.
  2. Run your favorite terminal emulator.
  3. In the terminal, run commands like below (replacing '--remote-debugging-port=9222' with any other command line flags you want to use):
    chromium-browser --remote-debugging-port=9222
    google-chrome --foo --bar=2

V8 Flags

V8 can take a number of flags as well, via Chrome's js-flags flag. For example, this traces V8 optimizations:

chrome.exe --js-flags='--trace-opt --trace-deopt --trace-bailout'

To get a listing of all possible V8 flags:

Chrome Canary Mac Os Download

Browse the V8 wiki for more flags for V8.

Android

Visit 'about:version' to review the flags that are effective in the app.

If you are running on a rooted device or using a debug build of Chromium, then you can set flags like so:

out/Default/bin/chrome_public_apk argv # Show existing flags.
out/Default/bin/content_shell_apk argv --args='--foo --bar' # Set new flags

You can also install, set flags, and launch with a single command:

out/Default/bin/chrome_public_apk run --args='--foo --bar'
out/Default/bin/content_shell_apk run # Clears any existing flags

For production build on a non-rooted device, you need to enable 'Enable command line on non-rooted devices' in chrome://flags, then set command line in /data/local/tmp/chrome-command-line. When doing that, mind that the first command line item should be a '_' (underscore) followed by the ones you actually need. Finally, manually restart Chrome ('Relaunch' from chrome://flags page might no be enough to trigger reading this file). See https://crbug.com/784947.

ContentShell on Android

There's an alternative method for setting flags with ContentShell that doesn't require building yourself:

  1. Download a LKGR build of Android.
  2. This will include both ChromePublic.apk and ContentShell.apk
  3. Install ContentShell APK to your device.
  4. Run this magic incantation
-a android.intent.action.VIEW
-n org.chromium.content_shell_apk/.ContentShellActivity

Canary Google Chrome

--esa commandLineArgs --show-paint-rects,--show-property-changed-rects

This will launch contentshell with the supplied flags. You can apply whatever commandLineArgs you want in that syntax.

Android WebView

This is documented in the chromium tree.

Chrome OS

Chrome Canary Mac Os X

  1. Put the device into dev mode, disable rootfs verification, and bring up a command prompt.
  2. Modify /etc/chrome_dev.conf (read the comments in the file for more details).
  3. Restart the UI via:
    sudo restart ui