Open
Bug 1418827
Opened 8 years ago
Updated 3 years ago
NotReadableError: Failed to allocate videosource on Win 10
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Core
WebRTC: Audio/Video
Tracking
()
NEW
People
(Reporter: achronop, Unassigned)
Details
Attachments
(3 files)
|
16.59 KB,
text/plain
|
Details | |
|
1.19 KB,
patch
|
Details | Diff | Splinter Review | |
|
66.21 KB,
text/plain
|
Details |
Model: Dell XPS 13
About Support:
Name Firefox
Version 59.0a1
Build ID 20171119100329
Update Channel nightly
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
OS Windows_NT 10.0
Steps
Go to gUM test page -> Video
(Audio along works)
| Reporter | ||
Comment 1•8 years ago
|
||
Logs with VideoEngine:5
Let me know if you need extra info
Assignee: nobody → mchiang
Alex, I cannot reproduce the bug with my Windows10 machine.
Could you help me apply the debug.patch and collect logs with VideoEngine:5?
Thanks.
Flags: needinfo?(achronop)
| Reporter | ||
Comment 3•8 years ago
|
||
Pushed on try because the target system does not have dev environment:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=83af0bb7378472d067df1280d282584b350aee3f
Flags: needinfo?(achronop)
| Reporter | ||
Comment 4•8 years ago
|
||
I have to say that today is working again. I could not make it not working and I did not manage to repro the crash. One thing to note is that antivirus asked for permissions in order to access the camera.
The logs attached are from opening the camera (gum test) on 3 tabs, all working correctly. That said if you don't see something obvious don't spend much time on that.
Updated•8 years ago
|
Rank: 20
Priority: -- → P3
Comment 5•7 years ago
|
||
I also have this problem in at least two Windows 10 machines.
Currently on Nightly 60.0a1.
OS Name Microsoft Windows 10 Pro
Version 10.0.14393 Build 14393
System Type x64-based PC
System has one Hauppauge ImpactVCB-e PCI video capture card and one StarTech composite to USB capture device.
https://mozilla.github.io/webrtc-landing/gum_test.html
video test shows a drop-down list for Camera to share:
USB 2861 Device
Hauppauge WinTV 885 Video Capture
In either case, the page displays "NotReadableError: Failed to allocate videosource"
The page works on Google Chrome on the same hardware and operating system.
There is no other application running which is using the camera.
A Java-based videoconferencing application also works normally.
A similar Hauppauge capture card works on the same page in Firefox 52.6.0 on CentOS 6, and on another computer running CentOS 7.
Comment 6•7 years ago
|
||
Also on https://webrtc.github.io/samples/src/content/devices/input-output/
in Firefox developer edition 60.0b4 (64-bit)
on Windows 10 Pro version 1709 build 16299.125
main.js:116:3
MediaStreamError { name: "NotReadableError", message: "Failed to allocate videosource", constraint: "", stack: "" }
again, works in Google Chrome
Comment 7•7 years ago
|
||
Similar result in Windows 10 with a new Firefox profile, and with Windows started in "diagnostic startup" - basic devices and services only. I.e. no other applications running that could have allocated the camera card.
Updated•3 years ago
|
Assignee: bonchiang → nobody
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•