Experiencing exact same issue on Version 57.0.2961.0 (Official Build) canary (64-bit).

No error, nothing, just closes. 

I disabled hardware acceleration for now to see if it resolves the problem.

Same exact issue.

Version 57.0.2961.0 canary (64-bit)

This issue happened to some people back in september with 57 too..
looks like an update fixed.. we'll have to wait and use regular :'(

Same issue, with same specs as original post.
The 'regular' nature of the crashes is likely a hint to Dev's, crashes every session between 5-10mins (havent imed yet).
I've tried the very basics: restarting, disabling all extensions (--no-extensions), disabling AV realtime(WinDefndr). 
Debug.log begins with:

[1011/141451:ERROR:process_info.cc(608)] range at 0xb56f25f000000000, size 0x19f fully unreadable
[1011/141451:ERROR:process_info.cc(608)] range at 0xb56f261000000000, size 0x19f fully unreadable
[1011/141451:ERROR:process_info.cc(608)] range at 0x0, size 0x19f fully unreadable
[1011/141451:WARNING:in_range_cast.h(38)] value 1785532001518 out of range
[1011/141451:WARNING:in_range_cast.h(38)] value 1785532000906 out of range
[1011/141451:WARNING:in_range_cast.h(38)] value 1785532003414 out of range
[1011/141451:WARNING:in_range_cast.h(38)] value 1785531999918 out of range 

I had the same problem and it was reproducible by trying to update the "Signed Tree Heads" component via chrome://components/ (check for update -> browser crash)

Workaround that fixed the crashes for me: Update the component in a regular chrome version and copy "CertificateTransparency\<current version (atm 252)>" to your canary Chrome appdata folder.

Just tried the workaround - I can confirm that Check for update crashes my browser directly, but copying the 252 folder form the stable release did not fix the problem for me - It still crashes after several minutes (Last time was after 7 mintues)

Replacing it with version 252 fixed it for me. I had also deleted 251 to make sure it didn't get loaded, have your tried that atgard?

Yes, you are right.
At first I didn't delete the 251, and it crashed on me. After relaunching Chrome, it deleted the old version by itself, and since then there were no crashes.
Thanks for the workaround.

I can also confirm the workaround posted by pcgo (Comment 6) works.
I deleted 251 after copying 252 and before launching Chrome.
Thanks for posting.

Can somebody upload a copy of the standard version files for the
workaround? I'd appreciate it very much.

I hope this'll do

Deleted: 252.zip 8.6 KB

252.zip 8.6 KB Download

thanks pcgo and rra!

Chrome Canary 57.0.2962.0 also happens the same problem.

heck dude, me too!! 

can you go to chrome://crashes and get the crash ids?

they say "Server ID: xxxxxxxxx0000000"

Same. Crashes every few minutes. I use the browser for work so this is a pain. Version 57.0.2962.0 (Official Build) canary (64-bit). No error code given, just exits.

is happening again ans is the same issue

Yep.. it magically was fine for a while yesterday, now at 57.0.2962.0 it's happening again

Yes I have found the issue has returned, and the '252' workaround is no longer working. I uploaded one crash report: Server ID: 44666b2080000000.

realit here's 253

Deleted: 253.zip 7.8 KB

253.zip 7.8 KB Download

Thanks rra! I missed that this issue has been merged so will keep an eye on 	 issue 676960  going fwd.