Bug 189736 - Get User Media | Safari | Angular 6
Summary: Get User Media | Safari | Angular 6
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebRTC (show other bugs)
Version: Safari 11
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-19 01:57 PDT by Robert
Modified: 2022-07-01 16:54 PDT (History)
5 users (show)

See Also:


Attachments
Error in console (60.47 KB, image/png)
2018-09-19 01:57 PDT, Robert
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert 2018-09-19 01:57:24 PDT
Created attachment 350098 [details]
Error in console

Hello! I need help with getting video stream from camera.

[Angular 6] Problem description:

The error is invoked only in Safari webrowser (updated to the latest version) and only on Mac. When we're trying to get video stream from camera through method navigator.mediaDevices.getUserMedia({video: true}, the webbrowser returns error: 
"NotReadableError: The I/O read operation failed.".

Ofcourse the camera device is connected, and it's not used by the another process.

The strange thing is that this error is invoked randomly - it means that one day we cannot reproduce error, and on the other day we can't get video stream through whole day. Important information - this error is invoked only if we try to het video stream from Angular app, if we try to get stream without Angular method works perfectly.

We tried to use runOutsideAngular method from zone.js, but without any success.

Does anybody had this kind of problem? Could you help us with that?
Comment 1 youenn fablet 2018-09-19 08:29:30 PDT
It might be bug 188309.
Is angular doing several getUserMedia call, first with audio, then with video?
Comment 2 Robert 2018-09-19 22:18:40 PDT
Not - it one call.
Comment 3 Raship Shah 2018-10-22 14:37:02 PDT
Most likely an hardware issue. I've been using it with Angular 6 ever since it came out, with no issues.
Comment 4 Eric Carlson 2018-10-31 05:59:06 PDT
(In reply to Raship Shah from comment #3)
> Most likely an hardware issue. I've been using it with Angular 6 ever since
> it came out, with no issues.

Can we close this report then?
Comment 5 Robert 2018-10-31 07:11:55 PDT
Unfortunetly not - we didn't find solution for that...
Comment 6 youenn fablet 2018-10-31 07:18:11 PDT
(In reply to Robert from comment #5)
> Unfortunetly not - we didn't find solution for that...

Do you have a repro case like a jsfiddle?
That would be really helpful.
Comment 7 Brent Fulgham 2022-07-01 16:54:43 PDT
Closing issue due to age and lack of reproducible test case.