Try https://www.chromium.org/for-testers/enable-logging and attach the results here.

This is happening for me too. Same versions of Chrome Canary and MacOS.

All I see in chrome_debug.log is:

[45586:775:0623/150411.325103:VERBOSE1:pref_proxy_config_tracker_impl.cc(154)] 0x7fcffb627010: set chrome proxy config service to 0x7fcffb627b40

I am able to open it by removing cache and preferences throug:

rm -rf Caches/Google/Chrome\ Canary Preferences/com.google.Chrome.canary.plist Saved\ Application\ State/com.google.Chrome.canary.savedState Application\ Support/Google/Chrome\ Canary/

It will open a fresh installation and prompt to submit data to Google and run normally until closed. Then it will crash again when opening.

This is the output of the system console:

default	14:11:52.460263 +0100	ksinstall	UNIX error exception: 17
default	14:11:52.460664 +0100	ksinstall	0x20087b0 opened /private/var/db/mds/system/mdsDirectory.db: 50744 bytes
default	14:11:52.462760 +0100	ksinstall	UNIX error exception: 17
default	14:11:52.463390 +0100	ksinstall	UNIX error exception: 17

Same symptom here, same one-line chrome_debug.log with verbose enabled:

~/Library/Application Support/Google/Chrome Canary$ less chrome_debug.log
[12459:775:0623/222500.142055:VERBOSE1:pref_proxy_config_tracker_impl.cc(154)] 0x7f9218ca6700: set chrome proxy config service to 0x7f9218ca7210

Crash report contents attached.

Deleted: crash_report.txt 60.5 KB

crash_report.txt 60.5 KB View Download

The same on Windows 7 x64 after today update: canary process shows up in process manager (without a GUI window) and disappears after some seconds.

Same issue here. Crashed upon update restart.

Content of the chrome_debug.log after --enable-logging --v=1:

[4904:4196:0623/163619.088:VERBOSE1:policy_loader_win.cc(376)] Reading policy from the registry is disabled.
[4904:4196:0623/163619.110:VERBOSE1:pref_proxy_config_tracker_impl.cc(154)] 00000000057FF730: set chrome proxy config service to 000000000223DFF0 

See also  Issue 736252 

Same issue, also on Mac OS 10.12.5 with Chrome Canary 61.0.3139.0 (MacBook Pro 2017)

Launched with `--enable-logging=stderr --v=1` yields similar output to that of others:

[1326:775:0623/145239.112486:VERBOSE1:pref_proxy_config_tracker_impl.cc(154)] 0x7fc5a166b680: set chrome proxy config service to 0x7fc5a166c160
Trace/BPT trap: 5


Attached is the crash report generated and displayed by Mac OS when the application crashes. Crashes started after relaunching to use latest update.

Deleted: apple-crash-report.log 60.3 KB

apple-crash-report.log 60.3 KB View Download

We're seeing users starting to report this in large volume (20+ cases) on the Chrome forum this morning: https://productforums.google.com/forum/#!topic/chrome/SQcsvAdF8-E.

Looks like the team is on it, I'll keep an eye on the Google-only access bug and keep them informed with updates once this is resolved. Let me know if you need anything for me to collect from users if the team needs it.

Same issues here, attaching yet another crash report

Deleted: canary-crash.txt 61.0 KB

canary-crash.txt 61.0 KB View Download

cat ~/Library/Application\ Support/Google/Chrome\ Canary/chrome_debug.log 


[72588:775:0623/180004.611904:VERBOSE1:pref_proxy_config_tracker_impl.cc(154)] 0x7fa63fd111f0: set chrome proxy config service to 0x7fa63fd11ca0

the same issue on mac

I was having the same issue on 61.0.3139.0. Downloaded 61.0.3139.4 from https://www.google.com/chrome/browser/canary.html, installed it on my mac (hit replace when prompted) and all is working again.

I confirm it no longer crashes in 61.0.3139.4 & newer.

I can confirm, that the issue still exist in 61.0.3141.0 on Windows 10.

The command line is:

C:\Users\ferdipr\AppData\Local\Google\Chrome SxS\Application\chrome.exe --user-data-dir=C:\Users\ferdipr\AppData\Local\Temp\karma-71045238 --no-default-browser-check --no-first-run --disable-default-apps --disable-popup-blocking --disable-translate --disable-background-timer-throttling --disable-renderer-backgrounding --disable-device-discovery-notifications http://localhost:9876/?id=71045238 --js-flags=--nocrankshaft --noopt --headless --disable-gpu --remote-debugging-port=9222

I attached console output, debug log and crash dump.

Deleted: console.log 9.1 KB

console.log 9.1 KB View Download

Deleted: debug.log 5.7 KB

debug.log 5.7 KB View Download

Deleted: 30615bf7-18eb-40b3-ab0a-202932b3582a.dmp 2.8 MB

30615bf7-18eb-40b3-ab0a-202932b3582a.dmp 2.8 MB Download

It appears, that the crash, when starting in the headless mode, has been fixed in the build 61.0.3143.0. No problems on Windows 10. Thanks!

The same crash on Windows 7 with 61.0.3157.0 

The same issue in MacOS version Google Chrome 61.0.3157.0 canary. 
exiting with the following message:
Segmentation fault: 11

61.0.3157.3 is OK.