Closed
Bug 1402905
Opened 7 years ago
Closed 7 years ago
Cannot access camera device from multiple content processes on Linux
Categories
(Core :: WebRTC: Audio/Video, defect, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 1399413
Tracking | Status | |
---|---|---|
thunderbird_esr52 | --- | unaffected |
firefox-esr52 | --- | unaffected |
firefox55 | --- | wontfix |
firefox56 | --- | wontfix |
firefox57 | --- | wontfix |
firefox58 | --- | wontfix |
firefox59 | --- | fixed |
People
(Reporter: pehrsons, Unassigned)
References
Details
(Keywords: regression)
I can repro this on Ubuntu 17.04 with Nightly from 20170912.
STR:
1. Open a tab and go to [1]. Click Video and approve.
2. Open another tab, and by hovering the tabs with the mouse, ensure that the process ids are different.
3. In the new tab from point 2, go to [1], click Video and approve.
Expected:
The camera stream would show up and play.
Actual:
"InternalError: Starting video failed" displayed on the page.
[1] https://mozilla.github.io/webrtc-landing/gum_test.html
Reporter | ||
Comment 1•7 years ago
|
||
Unsurprisingly mozregression gives bug 1303113 as the cause.
Blocks: 1303113
Updated•7 years ago
|
Rank: 13
Priority: -- → P2
See Also: → 1399413
Summary: Cannot access camera device from multiple content processes → Cannot access camera device from multiple content processes on Linux
Updated•7 years ago
|
status-firefox55:
--- → affected
status-firefox56:
--- → affected
status-firefox57:
--- → affected
status-firefox58:
--- → affected
status-firefox-esr52:
--- → unaffected
tracking-firefox58:
--- → ?
Updated•7 years ago
|
Keywords: regression
OS: Unspecified → Linux
Comment 2•7 years ago
|
||
Andreas, thanks for filing this as requested. I found bug 1399413 which was already filed. Seems to be the same issue.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
tracking-firefox58:
? → ---
Updated•7 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•