Closed
Bug 1365850
Opened 8 years ago
Closed 7 years ago
Intermittent browser/base/content/test/webrtc/browser_devices_get_user_media_queue_request.js | received error: NotReadableError: Failed to allocate videosource - Got ok, expected error: NotReadableError: Failed to allocate videosource
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 861716
| backlog | tech-debt |
People
(Reporter: mchiang, Unassigned)
Details
No description provided.
|
Reporter | |
Updated•8 years ago
|
OS: Unspecified → Linux
|
||
Comment 1•8 years ago
|
||
It is unclear how common this is.
backlog: --- → tech-debt
Rank: 35
Priority: -- → P3
|
|
Reporter | |
Comment 2•7 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=7c8c52fcc12cb1b37ffefee78b5226b051f221b3
Somehow on Linux try machine, gUM({ video: { deviceId: 'bad device' }, fake: true }) failed to provoke NotReadable error.
This issue doesn't occur on my local Linux machine.
Still figuring out.
|
|
Reporter | |
Comment 3•7 years ago
|
||
On the Linux try machine, gUM({ video: { deviceId: 'bad device' }, fake: true }) doesn't create a fake backend.
Only fake backend would provoke a NotReadable error when the constraint contains the keyword 'bad device'
|
|
Reporter | |
Comment 4•7 years ago
|
||
This bug has been addressed in bug 861716.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•