Steps to reproduce the problem:
1. open Chrome

What is the expected behavior?
Chrome opens

What went wrong?
Chrome crashes

09-01 09:27:47.082  9441  9441 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 9441 (m.chrome.canary)
09-01 09:27:47.083  3094  3094 W         : debuggerd: handling request: pid=9441 uid=10240 gid=10240 tid=9441
09-01 09:27:47.173  9512  9512 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-01 09:27:47.173  9512  9512 F DEBUG   : Build fingerprint: 'samsung/heroltexx/herolte:7.0/NRD90M/G930FXXU1DQG1:user/release-keys'
09-01 09:27:47.173  9512  9512 F DEBUG   : Revision: '8'
09-01 09:27:47.173  9512  9512 F DEBUG   : ABI: 'arm'
09-01 09:27:47.173  9512  9512 F DEBUG   : pid: 9441, tid: 9441, name: m.chrome.canary  >>> com.chrome.canary <<<
09-01 09:27:47.173  9512  9512 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
09-01 09:27:47.173  9512  9512 F DEBUG   :     r0 00000000  r1 ffb92204  r2 da8ed24f  r3 dc0b2dc4
09-01 09:27:47.173  9512  9512 F DEBUG   :     r4 dc137b4c  r5 daa30771  r6 ffb92224  r7 dc08e274
09-01 09:27:47.173  9512  9512 F DEBUG   :     r8 f2548780  r9 dc0b2dc8  sl 00000000  fp e3add500
09-01 09:27:47.174  9512  9512 F DEBUG   :     ip dc08da84  sp ffb92210  lr d94d05ad  pc d94d0492  cpsr a0070030
09-01 09:27:47.175  9512  9512 F DEBUG   : 
09-01 09:27:47.175  9512  9512 F DEBUG   : backtrace:
09-01 09:27:47.175  9512  9512 F DEBUG   :     #00 pc 0030f492  /data/app/com.chrome.canary-1/base.apk (offset 0x42af000)

Crashed report ID: 22f46fcc-52a0-4ec6-685e588d-775d95b9 but it cannot/it wasn't probably sent anywhere

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? Yes Released two days ago (around Wed)

Chrome version: 62.0.3201.4  Channel: canary
OS Version: 7
Flash Version: 

Cleaning data doesn't help, all other things also not.