Closed
Bug 782191
Opened 12 years ago
Closed 12 years ago
Only begin streaming video/audio from camera/recording device when needed through mozGetUserMedia
Categories
(Core :: WebRTC: Audio/Video, defect)
Core
WebRTC: Audio/Video
Tracking
()
VERIFIED
FIXED
People
(Reporter: jsmith, Assigned: anant)
Details
(Whiteboard: [getUserMedia], [blocking-gum-])
Attachments
(1 file)
352 bytes,
text/html
|
Details |
In comparing Chrome's production implementation to our Nightly implementation, one big difference I noticed was that they only appear to request access to the camera when they actually need it, not just immediately grab and lock the resource right after the mozGetUserMedia callback (i.e. lazy loading). This seems logical that they do this, as it prevents use of a resource that's not actively in use. We should follow suit here and only lock the camera for use when we actually need it post a mozGetUserMedia callback, and not do what we are doing now.
Reporter | ||
Updated•12 years ago
|
Whiteboard: [getUserMedia]
Reporter | ||
Comment 1•12 years ago
|
||
Confirmed this happens with the attached test case. We haven't started the content at all this test case - we've only made the gUM call and did console output. We shouldn't make the camera active in this case.
Keywords: qawanted
Reporter | ||
Comment 2•12 years ago
|
||
Reporter | ||
Updated•12 years ago
|
Assignee: nobody → mreavy
Whiteboard: [getUserMedia] → [getUserMedia], [blocking-gum-]
Assignee | ||
Comment 3•12 years ago
|
||
Bug 802411 should have fixed this.
Assignee: mreavy → anant
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•12 years ago
|
||
Verified on 10/19 build. This needs a test too.
Reporter | ||
Comment 5•12 years ago
|
||
No longer valid behavior given changed requirements, so no need to track for in-testsuite.
Flags: in-testsuite? → in-testsuite-
You need to log in
before you can comment on or make changes to this bug.
Description
•