New issue
Advanced search Search tips

Issue 922919 link

Starred by 7 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

getUserMedia does not throw error is video source is unavailable

Reported by reniar...@gmail.com, Jan 17 (5 days ago)

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce the problem:
1. Occupy your camera(s) in other process(es)
2. Navigate to any page that tries to call getUserMedia with video constraints (such as https://webrtc.github.io/samples/src/content/getusermedia/gum/ )
3. no errors are thrown, and the resulting stream is empty (displays a black image if rendered)

What is the expected behavior?
I would expect getUserMedia to throw NotReadableError (as it would by spec) instead of resolving with an unusable stream.

What went wrong?
good question, I don't have a good answer to that. Most of the time, it resolves with an unusable stream, with certain devices (some built-in laptop cameras), it gets stuck in getUserMedia without resolving/rejecting until I free the camera device in another application, and even then it resolves with an unusable stream.

Did this work before? Yes no idea, it's complicated to find and run older versions. I remember it working at least a year ago

Does this work in other browsers? Yes

Chrome version: 71.0.3578.98  Channel: stable
OS Version: 10.0
Flash Version: 

It does not seem to affect mac/linux users, I did not try older versions of windows either (definitely broken on 1809 build 17763.253). I've tried this on a variety of machines, including desktop computers and laptops.
 
chrome_debug.log
6.5 KB View Download
gumIssue.png
21.3 KB View Download

Comment 1 by philipp....@googlemail.com, Jan 17 (5 days ago)

Components: -Blink>WebRTC Blink>GetUserMedia>Webcam
guido, this used to work, right?

Comment 2 by guidou@chromium.org, Jan 17 (5 days ago)

Labels: Needs-Feedback
Owner: guidou@chromium.org
Status: Assigned (was: Unconfirmed)
Will try to bisect on Windows. I confirmed that this works fine on Linux stable and ToT and that it is broken on Windows stable (71) and canary (73).

Comment 3 by guidou@chromium.org, Jan 17 (5 days ago)

Owner: chfremer@chromium.org
The issue is reproducible with MediaFoundationVideoCapture enabled and is not reproducible with it disabled.
I tried bisecting to see if (with MediaFoundation forced) it was possible to find the place where the bug started, but it was broken from as far as r511593 back in 2017.

Assigning to chfremer@ for further investigation.

Comment 4 by chfremer@google.com, Jan 17 (5 days ago)

Thanks for making me aware of this!
To help the investigation, could you please list all the devices where this has happened? Ideally including the 9-character vendor+model ids as reported on the video capture tab at chrome://media-internals, e.g. "HD Pro Webcam C920 (046d:082d)".

Comment 5 by guidou@chromium.org, Jan 17 (5 days ago)

The one I tried is reported as "Integrated Webcam (1bcf:2b95)".
It's the built-in camera in a Dell Precision 5520.

Comment 6 by philipp....@googlemail.com, Jan 17 (5 days ago)

can reproduce with a surface laptop on Windows in M71, media-internals shows it as using media foundation. Disabling MediaFoundation as indicated in https://bugs.chromium.org/p/chromium/issues/detail?id=849636#c10 leads to a NotReadableError.

Comment 7 by guidou@chromium.org, Yesterday (41 hours ago)

Cc: guidou@chromium.org santhoshkumar@chromium.org
 Issue 920942  has been merged into this issue.

Comment 8 Deleted

Comment 9 by naicuoct...@gmail.com, Today (15 hours ago)

This used to work. 

In Nov 2017 I wrote an article covering all the errors (https://addpipe.com/blog/common-getusermedia-errors/). Chrome's errors were not up to spec at that time so it threw TrackStartError instead of NotReadableError.

Comment 10 by guidou@chromium.org, Today (15 hours ago)

#9: That is correct. This is a Windows-specific bug related to a switch to MediaFoundation as the library for video capture.

Sign in to add a comment