Tested on Pixel Android 8 and Samsung J7 Android 7.0.0 using Chrome #64.0.3282.137 & Canary #67.0.3361.0 and observed the text "The smallest video thing possible" and Camera of the device doesn't seems to be accessed. 

However, when the file is accessed through FireFox, device camera is switched on.

david@ -- Thanks for reporting this issue. Could you please confirm if the above mentioned behavior is the issue or anything else and is the issue device specific? If anything, could you please share the Good and Bad behavior. This would help us in reproducing and triaging the issue further.

Thanks in advance!

Yes, I believe you have recreated the bug. I thought it was device specific but seeing as you have recreated it on different devices I guess it is not device specific.

Thank you for providing more feedback. Adding the requester to the cc list.

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

Tested the issue in Android and able to reproduce the issue. Similar behavior is observed since Chrome #61.0.3116.0

Steps Followed:
1. Launched the Chrome Browser.
2. Open the sample HTML file in the original comment
3. Observed the text "The smallest video thing possible" message is displayed and camera of the device is not accessed.

However, in the FireFox mobile version, camera is accessed.

Chrome versions tested:
61.0.3116.0, 65.0.3325.109(Stable), 67.0.3365.0(Canary)

OS:
Android 8.1

Android Devices:
Pixel XL, Pixel

This seems to be a Non-Regression issue as same behavior is seen since M61. Untriaged for further input's on this issue.

Please navigate to below link for log's and screen cast--
go/chrome-androidlogs/818003

Note: 
1. This issue is not observed in Desktop. 
2. For the earlier version of Chrome before and for M-60, "Aw-Snap.." error is seen.
3. Issue is not observed on FireFox mobile version.

Thanks!

Sounds like this could be a capture issue. Magjed, what do you think?

Chromium uses their own video capturers independent of the implementations we have in Mobile WebRTC, so I'm not familiar with this. I'm not sure who the owner is for the Android video capturer in Chrome. I'm assigning to Christian, hopefully he knows.

I am not an expert on the JavaScript side of things, but when comparing the JavaScript from the report to the one from https://webrtc.github.io/samples/src/content/getusermedia/gum/, which does not seem to have that issue, I see the following difference. Instead of 

  video.src = window.URL.createObjectURL(stream);
  video.play();

it does

  video.srcObject = stream;

Is that what makes a difference between working and not working?

srcOjbect is listed as an experimental feature. It may be in Canary but shouldn't the other solution still work? As I stated earlier the same code works fine on Firefox, I have also tested on Opera and it works there as well.