Update :
Above issue is not seen on Linux(14.04 LTS) OS with canary build (61.0.3157.0) and will update Mac OS info once Mac(#61.0.3157.0)build is available.

Note : 
1. Unable to provide crash id as build does not launch at all.
2. Unable to provide build revision number from chrome://version since build crashes on every launch.

Kindly refer an attached screen cast for the reference.

Deleted: Actual_Result.mp4 800 KB

	Actual_Result.mp4 800 KB View Download

Update : 
Above crash is also observed on Mac(10.11.6,10.12.3) OS. Mac build (#61.0.3157.0) keeps crashing on every launch.

Using the per-revision bisect providing the bisect results,
Good build:61.0.3156.0(Revision:486205).
Bad build:61.0.3157.0(Revision:486615).

You are probably looking for a change made after 486589 (known good), but no later than 486590 (first known bad).

CHANGE-LOG URL:
---------------
 https://chromium.googlesource.com/chromium/src/+log/7abded67c558f90345373b1a4e3cf886f4191557..34b11e87de7293a6fb4768184d755ad594b7ab8e

From the CL above, assigning the issue to the concern owner

@kmilka : Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Reviewd-on: https://chromium-review.googlesource.com/561922

Note :Able to reproduce the issue in Win 10.0,Mac 10.12.3 and not in Ubuntu 14.04.
Adding Release Block-Dev for this issue.Please remove if not the case.

Cc'ing asvitkine@(reviewer) and Looping stability sheriff label for help in reverting/fixing this.

Please find the stack Trace of the issue:

Stack Trace:
------------
Thread 0 (id: 1823700) CRASHED [EXC_BAD_ACCESS / KERN_INVALID_ADDRESS @ 0x00000000 ] MAGIC SIGNATURE THREAD
Stack Quality76%Show frame trust levels
0x00000001108fe59b	(Google Chrome Framework -variations_field_trial_creator.cc:213 )	variations::VariationsFieldTrialCreator::GetClientFilterableStateForVersion(base::Version const&)
0x00000001108fe31e	(Google Chrome Framework -variations_field_trial_creator.cc:176 )	variations::VariationsFieldTrialCreator::CreateTrialsFromSeed(std::__1::unique_ptr<base::FieldTrial::EntropyProvider const, std::__1::default_delete<base::FieldTrial::EntropyProvider const> >, base::FeatureList*)
0x0000000110900984	(Google Chrome Framework -variations_service.cc:646 )	variations::VariationsService::CreateTrialsFromSeed(base::FeatureList*)
0x000000010ea8326f	(Google Chrome Framework -chrome_browser_main.cc:746 )	ChromeBrowserMainParts::SetupFieldTrials()
0x000000010ea85480	(Google Chrome Framework -chrome_browser_main.cc:1231 )	ChromeBrowserMainParts::PreCreateThreadsImpl()
0x000000010ea845ad	(Google Chrome Framework -chrome_browser_main.cc:956 )	ChromeBrowserMainParts::PreCreateThreads()
0x000000010d99bebb	(Google Chrome Framework -browser_main_loop.cc:803 )	content::BrowserMainLoop::PreCreateThreads()
0x000000010dd1fb86	(Google Chrome Framework -callback.h:80 )	content::StartupTaskRunner::RunAllTasksNow()
0x000000010d99c488	(Google Chrome Framework -browser_main_loop.cc:925 )	content::BrowserMainLoop::CreateStartupTasks()
0x000000010d9a0533	(Google Chrome Framework -browser_main_runner.cc:127 )	content::BrowserMainRunnerImpl::Initialize(content::MainFunctionParams const&)
0x000000010d99a0b3	(Google Chrome Framework -browser_main.cc:42 )	content::BrowserMain(content::MainFunctionParams const&)
0x000000010ea3ddcf	(Google Chrome Framework -content_main_runner.cc:686 )	content::ContentMainRunnerImpl::Run()
0x000000011035f223	(Google Chrome Framework -main.cc:469 )	service_manager::Main(service_manager::MainParams const&)
0x000000010ea3d3b3	(Google Chrome Framework -content_main.cc:19 )	content::ContentMain(content::ContentMainParams const&)
0x000000010d3b5bb7	(Google Chrome Framework -chrome_main.cc:132 )	ChromeMain
0x000000010d338dd3	(Google Chrome Canary + 0x00000dd3 )	
0x00007fffa68ce234	(libdyld.dylib + 0x00005234 )	start

This is also happening on macOS 10.12.5

Deleted: canary-macos.txt 90.0 KB

canary-macos.txt 90.0 KB View Download

 Issue 742879  has been merged into this issue.

 Issue 742898  has been merged into this issue.

This is the top browser crash reported for Canary Version 61.0.3157.0. Below link gives in detail for the total number of instances (524) in which the crash has reported on MAC OS (3hrs data since pushed to users).

https://goto.google.com/nuaai

Windows canary is not out yet, will update the details once data is available.

Thanks.!

 Issue 742988  has been merged into this issue.

 Issue 742969  has been merged into this issue.

 Issue 742928  has been merged into this issue.

As per Comment #9 updating windows canary details.
1.This is the top crash in windows canary # 61.0.3157.0 and seeing 5798 from 4341 different clients.

61.0.3157.0	93.36%	7921		-Canary

Link to the list of builds:
---------------------------
https://goto.google.com/ntvvh

Thank You!

I am experiencing the same issue on Windows 10 and Android O with the version of Canary that was released today 

 Issue 742982  has been merged into this issue.

Adding other platforms where this also happens. 

I'm also seeing this with Version 61.0.3157.0 (3157.0) on Mac OS X 10.12.6 (16G24b)

Crashed Thread:        0  CrBrowserMain  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000

Thanks!

Clicked Revert on the CL: https://chromium-review.googlesource.com/c/571920

Issue 742997 has been merged into this issue.

Thank you  asvitkine@. Could you please merge the revert listed at #18 to Canary branch #3157 so we can trigger new canary from same branch.

Note: Merge approval is not needed.

Done.

(I do wonder whether we should have better process than waiting for earliest timezone eng to come online to do this - i.e. can't this be done by the folks who first notice the bugs? At least for top crashers like this one where it should just be a matter of reverting.)

Same issue, on W10 and W2008 R2

Same issue here, Windows 10 64bit 1703 (build 15063.483)

Marking as Fixed given we reverted the CL and merged the patch. (The canary respin should have it resolved.)

Canary build #61.0.3157.3 with revert is in progress for all OS. Thank you.

When and how do we get the previous version?

In a similar vein to #26. Fresh install still pointing to 3157.0 Is there an ETA for rollout completion?

Issue 742712 has been merged into this issue.

I restarted my mac machine and now my Chrome Canary is upgraded and not launching at all. Once the fix is available how will Chrome Canary update in my case? Do I have to delete and re-install?

It would be nice for us to be able to download older versions of Canary in case this happens again and we are unable to use Canary at all.

Same happens, Win10 64bit.

 Issue 743016  has been merged into this issue.

I second nelsonw, it would be nice to be able to install previous builds so we can self-revert in these cases.

4 hours after the rollout and still getting 3157. I've cleared out the installer download cache and Google keeps giving me the broken build.

A huge +1 to a listing of the previous X builds and links to the different platform downloads. A lot of developers use Canary while working, and problems like this can put a big crimp in the work day. 

Same here, just tried it on a new machine and still is downloading 3157.0 which does not work.

On Mac, you can force update by opening Terminal and running the command below (everything in one line). This will cause Google Software Update for Mac to start manual update process (typically the updater performs that automatically once in 5 hours).

~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/CheckForUpdatesNow.command || /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/CheckForUpdatesNow.command

Thanks for the tip!

Thanks for the tip borisv! That worked for me and updated me to 3157.3!

I am still getting the bad build pulled on a fresh install
on Win10 64bit.

I guess it must be a high cache timeout or propagation delay.

As #39 said, Im also still having that problem on a Win 10 64 bit... Nothing fixed.

Sorry for inconvenience everyone. Please update to Chrome version #61.0.3157.3 for Andorid and Mac to see the fix. Windows update is coming soon.

Canary now auto updates to 61.0.3157.3 on launch and is now working again. Downloading from the Canary site works too. Thanks for the fix. But seriously, previous builds should be downloadable too.

Just uninstalled, redownloaded and still getting 61.0.3157.0 on Windows 10.  :(

 Issue 743117  has been merged into this issue.

Can't launch Canary on Win 10

Is there anyway to updated straight to Chrome version #61.0.3157.3?

Just uninstalled and cleared the folders, new download only installed 3157.1 not .3

.3 is out for OS X

canary setup just got 3157.3 for Win10 finally - back and running in canary

61.0.3157.3 is available for Windows 32/64 bit as well.

Thank you Chromium Canary team for your hard work, back to normal now.

A trick to update Chrome Canary without having to download installer again from Google website is by launching this program manually:

C:\Users\%username%\AppData\Local\Google\Update\1.3.33.5\GoogleUpdateSetup.exe

Works fine now. Downloaded via Canary webpage instead of GoogleUpdateSetup.exe

Updated to 61.0.3158.0 and it still does not launch, still doing the exact same thing 61.0.3157.0 was doing on Win10.

*edit* that is NOT correct! So this is very odd, but after updating it looks like in the c:\user\name\appdata\local\google\chrome sxs\ application there was actually two versions sitting there, 3157 and 3158. There was two chrome.exe the new one named new_chrome.exe and I had to run new_chrome.exe which then renamed itself chrome.exe and deleted all the old 3157, and then started like it should. Very weird I had to go do that manually though.