Here is the terminal output:

$ chromium
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[23519:23557:0710/151811.431568:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: content_plugin from binding interface: memory_instrumentation::mojom::Coordinator exposed by: content_browser
ALSA lib pcm.c:8473:(snd_pcm_set_params) Unable to get period size for PLAYBACK: Invalid argument
chromium --show-component-extension-options --ignore-gpu-blacklist --no-default-browser-check --disable-pings --media-router=0 --enable-remote-extensions --ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so --ppapi-flash-version=24.0.0.194: pcm_params.c:170: snd1_pcm_hw_param_get_min: Assertion `!snd_interval_empty(i)' failed.
Received signal 6
#0 0x55b043464af6 <unknown>
#1 0x55b043464ed9 <unknown>
#2 0x7f3db63bf0c0 <unknown>
#3 0x7f3dab2d1fcf gsignal
#4 0x7f3dab2d33fa abort
#5 0x7f3dab2cae37 <unknown>
#6 0x7f3dab2caee2 __assert_fail
#7 0x7f3dadbfeafa <unknown>
#8 0x7f3dadc17da3 <unknown>
#9 0x7f3dadc004dc <unknown>
#10 0x7f3dadc1736d <unknown>
#11 0x7f3dadc00c8b <unknown>
#12 0x7f3dadc00f70 <unknown>
#13 0x7f3dadc014f0 <unknown>
#14 0x7f3dadc0157e <unknown>
#15 0x7f3dadc1753e <unknown>
#16 0x7f3dadc004c4 <unknown>
#17 0x7f3dadc1736d <unknown>
#18 0x7f3dadbfd9c3 snd_pcm_set_params
#19 0x55b041c66edb <unknown>
#20 0x55b041c67235 <unknown>
#21 0x55b041c65a92 <unknown>
#22 0x55b041c65c8b <unknown>
#23 0x55b041c59a8b <unknown>
#24 0x55b041c59d35 <unknown>
#25 0x55b041c5ac65 <unknown>
#26 0x55b041c5a408 <unknown>
#27 0x55b041c5505a <unknown>
#28 0x55b0434fa9f1 <unknown>
#29 0x55b043485c40 <unknown>
#30 0x55b0434878cd <unknown>
#31 0x55b043487d68 <unknown>
#32 0x55b043488b89 <unknown>
#33 0x55b043484ce5 <unknown>
#34 0x55b0434aa28a <unknown>
#35 0x55b0434c8936 <unknown>
#36 0x55b0434c3fe2 <unknown>
#37 0x7f3db63b5494 start_thread
#38 0x7f3dab387a8f clone
  r8: 0000000000000000  r9: 00007f3d8fe1e290 r10: 0000000000000008 r11: 0000000000000246
 r12: 00000000000000aa r13: 00007f3dadc71340 r14: 00001beb11cbc800 r15: 00001beb11f90a50
  di: 0000000000000002  si: 00007f3d8fe1e290  bp: 00007f3dadc6d2d3  bx: 0000000000000006
  dx: 0000000000000000  ax: 0000000000000000  cx: 00007f3dab2d1fcf  sp: 00007f3d8fe1e308
  ip: 00007f3dab2d1fcf efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

I see you're running the chromium-browser that ships with Ubuntu.  Could you either
1. File a bug with Canonical. (It's impossible for Google to get crash reports with Chromium)
2. Try with google-chrome-stable and if it still crashes, post the crash ID

No, my chromium definitely comes from the Debian Sid repository.

I was looking into it and I discovered the crash happened with ALSA set to certain period/buffer settings. My motherboard was released this year although somehow sound works - but seems to need adjustment.

Thank you for providing more feedback. Adding requester "pbommana@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

keanetoken@ as per comment #4, shall we close the issue?

ThanK You...

Why not fix the bug? It looks like the crash occurs right after starting a new thread and doing snd_pcm_set_params, when

version=24.0.0.194: pcm_params.c:170: snd1_pcm_hw_param_get_min: Assertion `!snd_interval_empty(i)' failed.

Perhaps Chromium just needs to account for snd_pcm_set_params not succeeding.

Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Adding respective component to route this to appropriate team. This looks similar to  Issue 360349  which was archived due to no update for long.

The assert failure isn't in Chromium code it's in the system ALSA audio stack; we do account for it failing. I think something is wrong with your audio driver installation.

reporter@, can you uninstall/reinstall your audio driver to see if it fix this bug?

There is no ALSA package in the Debian repository, I'm not sure how to reinstall it.

My testing has found that ALSA rejects all but a few different period/buffer settings for my soundcard (onboard sound for my Asus ROG Strix B350F Gaming motherboard) and I think in the case that caused Chromium to crash, it was actually using a period/buffer setting that was rejected by the soundcard for my chosen samplerate.

Thank you for providing more feedback. Adding requester "msrchandra@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Unable to triage this issue from TE end as it is related to ALSA packages.Could some one from dev team please look into this issue.Adding TE-NeedsTriageHelp label.

Thanks..!

dale, any idea?

It's a bug in ALSA, I'm not sure there's anything we can do. Certainly ALSA shouldn't crash if we ask it to play something it can't, it should just reject the playback.

We output at 48kHz with whatever channel layout the source media has. I recommend you install Pulse audio instead since the ALSA playback path in Chrome is not maintained (for reasons just like the crash you're seeing).