mediaDevices.getUserMedia occasionally fails to receive stream
Reported by
mbl...@phzio.com,
Oct 13 2017
|
||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Run an number of RTC sessions 2. On launch of a new session, sometimes, the camera is still active, but Chrome does not receive a stream. If there were no active sessions when this happens, the camera is not activated. No errors are reported by the Promise callback. 3. getUserMedia fails to return (to success or catch block) What is the expected behavior? Either report an error if there's a reason the camera can't be accessed or ensure consistent access to camera. What went wrong? Sometimes, the camera is still active, but Chrome does not receive a stream. Other times, if there were no active sessions when this happens, the camera is not activated. No errors are reported by the Promise callback Did this work before? N/A Chrome version: 61.0.3163.100 Channel: stable OS Version: 10.0 Flash Version:
,
Oct 16 2017
,
Oct 17 2017
,
Oct 17 2017
mblock@ Thanks for the issue. Can you please provide us the test URL where you are seeing this issue, which will help us in further investigation of the issue. Thanks..
,
Oct 17 2017
Though not strictly on this particular page, this page uses the same base code for the chat sessions: https://app.phzio.com/test-chat?uid=chromium-774485 Note this is a scratchpad, so the code base might change. The problem seems to be with the mediaDevices.getUserMedia call anyway, before any WebSocket or RTCPeerConnections are created.
,
Oct 17 2017
Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 18 2017
Unable to reproduce the issue on Win-10 using chrome reported version #61.0.3163.100 and latest canary #64.0.3242.0. Following are the steps followed to reproduce the issue. ------------ 1. Navigated to URL: https://app.phzio.com/test-chat?uid=chromium-774485. 2. When the camera was not activated got an error message as "We failed to get access to your camera. The following error was received:NotFoundError." 3. When the camera was active, consistent access to camera was observed. mblock@ - Could you please check the issue on latest canary #64.0.3242.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Also please let us know if we missed anything from our side. Thanks...!!
,
Oct 18 2017
I have my browser open right now exhibiting the problem. If you receive this in short order can you let me know if there is any debugging info I can give you
,
Oct 18 2017
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 18 2017
tried to disable and then re-enable my camera through device manager. No change. Chrome does not see that I have a camera available and reports no errors (no return on getUserMedia promise either for success or error catch)
,
Oct 18 2017
Relaunching using this protocol returns access to the camera: https://chromedevtools.github.io/devtools-protocol/ It asks for my permission to use the camera and then it works. However, the original tab opened before launching this way still cannot use the camera and gUM still doesn't return success or error from promise
,
Oct 18 2017
Okay - it seems that all audio is lost even when just browsing YouTube. Shutting down chrome completely and relaunching fixes it. Also, video loads from YouTube are also very slow. It suggests that something may be either local driver issues or that media in general is dropping in Chrome. Other applications loaded at the same time have no problem accessing and playing media devices.
,
Oct 20 2017
,
Dec 7 2017
mblock@: Any updates on this? Based on #12 it sounds like the issues you were seeing may not be specific to getUserMedia.
,
Dec 7 2017
Sorry for the disconnect. I haven't been able to reproduce it recently. That said, I've been doing less testing. For now, I'll consider this issue closed as it's not reliably repeatable to investigate. Thanks for your efforts.
,
Dec 7 2017
Thanks. Marking as WontFix. Let us reopen if you run into this again. |
||||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Oct 13 2017