Thanks for the report, having the files to reproduce the problem is appreciated.  When I run the vid_crash.js script, I get a log like this in the terminal:
CDP exception thrown: simple_video.html line 0 column 0 
CDP exception details: DOMException: Failed to load because no supported source was found. 

Also, if I remove the "--headless" flag from vid_crash.js, I'm able to see the chrome instance visually, open DevTools, and check the console.  Does this work on your setup?

Yes, that is precisely the problem. It works non-headless, does not work headless.

Apologies for forgetting to give you this, but the output when I run it is:

Test page URL: file:///Users/rjongbloed/Work/vid_crash/simple_video.html
Chrome started
CDP connected
CDP loading page: file:///Users/rjongbloed/Work/vid_crash/simple_video.html
CDP frameStartedLoading { frameId: '46906.1' }
CDP frameNavigated { frame: 
   { id: '46906.1',
     loaderId: '46906.1',
     url: 'file:///Users/rjongbloed/Work/vid_crash/simple_video.html',
     securityOrigin: 'file://',
     mimeType: 'text/html' } }
==============================================================
CDP target crashed! {} 
==============================================================

Thank you for providing more feedback. Adding requester "luoe@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

Thanks for the report and for providing the extra info to reproduce. 

I can confirm this failing on Canary on Mac. 
I see the following two errors: 

[0816/150927.384834:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[0816/150927.385045:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN


Looking into the code it looks like the call to avformat_open_input at:
https://cs.chromium.org/chromium/src/media/filters/ffmpeg_glue.cc?rcl=7149dfc6e7697ac89bf12c26a13946184ca40eea&l=148

returns AVERROR_INVALIDDATA. 

I'm not really sure why this is the case, maybe something needs to be added on Mac/Windows to add ffmpeg when running on headless mode

Maybe someone from the media team has an idea what's going wrong here?

That means we can't read the media file for some reason. Seems like the video source you're using might be failing CORS? If you download the video and run it from the same file:// location does it fail?

It appears that somewhere between 62.0.3182.0 and 62.0.3187.0 the problem has been fixed!

If someone did something, thank you very much!

Confirmed this is working now on canary