Bug 189736

Summary: Get User Media | Safari | Angular 6
Product: WebKit Reporter: Robert <robert-juszczyk>
Component: WebRTCAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: bfulgham, eric.carlson, robert-juszczyk, shahraship, youennf
Priority: P2    
Version: Safari 11   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Error in console none

Robert
Reported 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?
Attachments
Error in console (60.47 KB, image/png)
2018-09-19 01:57 PDT, Robert 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
youenn fablet
Comment 1 2018-09-19 08:29:30 PDT
It might be bug 188309. Is angular doing several getUserMedia call, first with audio, then with video?
Robert
Comment 2 2018-09-19 22:18:40 PDT
Not - it one call.
Raship Shah
Comment 3 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.
Eric Carlson
Comment 4 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?
Robert
Comment 5 2018-10-31 07:11:55 PDT
Unfortunetly not - we didn't find solution for that...
youenn fablet
Comment 6 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.
Brent Fulgham
Comment 7 2022-07-01 16:54:43 PDT
Closing issue due to age and lack of reproducible test case.
Note You need to log in before you can comment on or make changes to this bug.