I was able to reproduce the issue. UI log is full of errors like this:

<snip>
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
libEGL warning: MESA-LOADER: failed to retrieve device information

libEGL warning: DRI2: failed to open vgem (search paths /usr/lib64/dri)
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
Received signal 11 SEGV_MAPERR 000000000008
#0 0x0385780f2bac <unknown>
#1 0x0385780f2701 <unknown>
#2 0x79af67e9d2e0 <unknown>
#3 0x79af67488600 <unknown>
  r8: 0000000000000003  r9: 00001111b22fde60 r10: 0000000000000000 r11: 0000038576563900
 r12: 0000000000000030 r13: 0000000020203852 r14: 00001111b231fbe0 r15: 000079af60de18f8
  di: 0000000000000000  si: 0000000020203852  bp: 000079af60de18a0  bx: 0000000000000000
  dx: 0000000000020008  ax: 0000000000000000  cx: 0000000000000003  sp: 000079af60de17d8
  ip: 000079af67488600 efl: 0000000000010202 cgf: 0000000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000008
[end of stack trace]
Calling _exit(1). Core file will not be generated.
</snip>

It looks like this error repeats forever, as if chrome is trying to restart the process every time it segfaults. Just before that error goes infinite, there are a few suspicious errors:

[19862:19919:0810/133133.813884:ERROR:service_manager.cc(156)] Connection InterfaceProviderSpec prevented service: content_browser from binding interface: content::mojom::Child exposed by: nacl_loader
[1,156465024:20:31:33.932669] Native Client module will be loaded at base address 0x00001c3300000000
[1:15:0810/133142.521546:ERROR:adm_helpers.cc(62)] Failed to query stereo recording.
[19862:19862:0810/133144.474142:ERROR:devicetype.cc(31)] Unknown device type "OTHER"

I don't recognize them, however.

Yes, same thing here. I think we should move the conversation to  Issue 751234