+thestig

Is there a way to get the crash ID without the GUI?

Nvm, I see the crash IDs in OP's report

Are you running Chrome as root, by any chance?

@thomasanderson No.

What happens if you try launching with --no-sandbox

Bus error instead of Illegal instruction... 
-------------------------------------------------------------------------------
valandil ~ $ google-chrome-stable --no-sandbox
[0614/161111.130448:ERROR:nacl_helper_linux.cc(311)] NaCl helper process running without a sandbox!
Most likely you need to configure your SUID sandbox correctly
--2017-06-14 16:11:16--  https://clients2.google.com/cr/report
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving clients2.google.com... 172.217.2.110, 2607:f8b0:400b:80c::200e
Connecting to clients2.google.com|172.217.2.110|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/fd/4’

     0K    
 Crash dump id:  674e8dbbf0000000 
                                                  823K=0s

Bus error (core dumped)

I forgot to mention it here, but renaming .config/google-chrome and .cache/google-chrome fixes the issue. However, I would like very much to get back most of my profile information, hence the question.

Here's the Google Chrome Help Forum post: https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/chrome/3Fy9PsRQZ0s/GqyNK3BqAQAJ 

+agl

It looks like the crash is in sha256_block_data_order_avx (https://cs.chromium.org/chromium/src/third_party/boringssl/linux-x86_64/crypto/fipsmodule/sha256-x86_64.S?rcl=997174a8a84df91727a37259fb5ee7ea6ee7e1a2&l=2852)

Which CPU are you using?  It appears to not have the SHA instructions available.

Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz

Not sure how to check specifically for SHA, but it does have vector extensions, up to avx2 I believe.

valandil ~ $ cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 60
model name	: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
stepping	: 3
microcode	: 0x22
cpu MHz		: 1199.853
cache size	: 6144 KB
physical id	: 0
siblings	: 8
core id		: 0
cpu cores	: 4
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts
bugs		:
bogomips	: 4791.80
clflush size	: 64
cache_alignment	: 64
address sizes	: 39 bits physical, 48 bits virtual
power management:

That CPU is a Haswell, so it has AVX. Thus I don't believe that it's an illegal instruction. Looking at 674e8dbbf0000000, it's crashing while hashing a Flash file from components. I would guess that code is passing a bad pointer or length for hashing.

Is there anything in dmesg about I/O errors? A SIGBUS suggests that the file on disk may have been truncated between stat() and reading, or perhaps that there was an error from the underlying storage.

Oh yes, I think that's it! Is there something to do in this situation?

[  507.794305] ata6.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x0
[  507.794311] ata6.00: irq_stat 0x40000008
[  507.794315] ata6.00: failed command: READ FPDMA QUEUED
[  507.794321] ata6.00: cmd 60/08:18:e8:91:20/00:00:5c:00:00/40 tag 3 ncq dma 4096 in
                        res 41/40:00:e8:91:20/00:00:5c:00:00/40 Emask 0x409 (media error) <F>
[  507.794324] ata6.00: status: { DRDY ERR }
[  507.794326] ata6.00: error: { UNC }
[  507.806726] ata6.00: configured for UDMA/100
[  507.806742] sd 5:0:0:0: [sdb] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[  507.806745] sd 5:0:0:0: [sdb] tag#3 Sense Key : 0x3 [current] 
[  507.806747] sd 5:0:0:0: [sdb] tag#3 ASC=0x11 ASCQ=0x4 
[  507.806750] sd 5:0:0:0: [sdb] tag#3 CDB: opcode=0x28 28 00 5c 20 91 e8 00 00 08 00
[  507.806752] blk_update_request: I/O error, dev sdb, sector 1545638376
[  507.806791] ata6: EH complete
[  508.627034] traps: chrome[4527] trap invalid opcode ip:558d7c761dd4 sp:7fff30fbfd50 error:0 in chrome[558d7b494000+6adb000]

I think that would do it. I'm going to close this because it looks like you have disk errors. The SIGBUS would be delivered by the kernel when it failed to service a memory read in a mmaped region.

You probably want to do things like:

sudo smartctl -a /dev/sdb
man smartctl

and probably try coping all the data off that disk ASAP.

The SIGILL seems odd because it happened because the Zygote process failed to start. Normally that would be an abort()/SIGTRAP. However, if the disk is failing, all bets are off.