Seems like vp9.2 which should play in software. GVD is throwing a decode error on my Pixelbook though.

Please try this on a more recent version of chrome.

hubbe@ are you able to play the video in c#0? I can't in 62.0.3202.52.

Actually how did you create that file in c#0, lesleydeng0? vlc, firefox, and chrome refuse to play the file because they say it's broken. ffplay plays garbage.

No, I cannot play that file.
It shouldn't crash the webpage though.

Unable to play the video "test.webm" in comment#0.

@Reporter: Could you please respond to comment #4.

Thanks! 

Sorry for my delayed response.

Here in WebM(vp9 + opus) files, the vp9 video part is composed with multiple frames. I slightly altered the first video frame.
Each video frame has an uncompressed header, identified by "XX XX XX 49 83 42"(open this file in Sublime Text, the identifier is in line 42). After that indentifier is "00" in the attached original file and "04" in the newly attached file. That's the only place I altered.
The Hexadecimal "00" is '00000000' in bits and the 5th '0' means its CSS is in YUV and the later two '00' means its CSS value is 4:4:4.
And in "test-only..." file the "04" is '00000100' and the 5th '0' means YUV and the later '10' means its CSS is 4:2:2.

In the "test.webm" file I changed meta-data information in both audio track and first video frame header. Thus you may have better see the newly attached "test_only..." file to see whether it will trigger webpage crashes. In this file only the first video frame header is altered(lin 42 in ).

Deleted: test-only_video_altered.webm 1.1 MB

	test-only_video_altered.webm 1.1 MB View Download

Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

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

Hmm, why do you think that file should play? No player I have seems to play it.

I suppose the browser should either play the video file normally since the error in video frame header can be detected easily (none of popular browsers do, but I've seen tools to correct error in meta-data header), or, if it don't correct the errors, just report an error in the file (many browsers and Chrome in version 54.0 for android do).

The invalid media file should not cause the webpage to be crashed ( in Chrome and Opera in desktop ), since the errors can happen during networking in real word and I remember that some browsers have buffer mechanism, thus if such kind of error happens during the first loading process, the users may not be able to have the webpage loaded correctly by simply clicking reload button.

Are you able to reproduce any crash in m62+? The file just doesn't play for me. If you have a crash id from chrome://crashes I can take a look.

No crash in version 62.0.3202.62.

Is this problem solved in release upgrading?

M62 is our current public stable release, so there seems to be no more issue.