Closed
Bug 786081
Opened 13 years ago
Closed 13 years ago
Cannot stop a video already started from getUserMedia
Categories
(Core :: WebRTC: Audio/Video, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 784829
People
(Reporter: jsmith, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [getUserMedia], [blocking-gum+])
Steps:
1. Go to https://people.mozilla.com/~anarayanan/gum_test.html
2. Select video
3. Select stop
Expected:
The camera stream should stop running (no light on the user's webcam).
Actual:
The camera stream does not stop. As a result, if I try to start video, picture, or audio again, I'll fail out with an error saying HARDWARE_UNAVAILABLE for picture and video, NO_DEVICES_FOUND for audio.
Reporter | ||
Comment 1•13 years ago
|
||
This is an obvious blocker, so I'm automatically going to triage this.
Keywords: regression
Whiteboard: [getUserMedia], [blocking-gum+]
Reporter | ||
Comment 2•13 years ago
|
||
Also, ignore the issue I hit with audio in comment 0. That's the same old issue that you can't use audio twice with gUM.
Reporter | ||
Updated•13 years ago
|
Keywords: regressionwindow-wanted
Reporter | ||
Comment 3•13 years ago
|
||
Regression Range:
8/28 - Busted
8/27 - Busted
8/26 - Crashing bug evident (can't tell if it works or not)
8/24 - Crashing bug evident (can't tell if it works or not)
8/21 - Working
Reporter | ||
Comment 4•13 years ago
|
||
Roc - Do you have any ideas what might have caused this regression?
I know bug 785001 landed recently to fix the crash, but would that cause this regression? I see other bugs such as the ones below in the changelog as well:
* bug 785671
* bug 767480
Reporter | ||
Comment 5•13 years ago
|
||
Reporter | ||
Updated•13 years ago
|
Keywords: regressionwindow-wanted
Maybe bug 779715.
Comment 7•13 years ago
|
||
I can confirm using this program:
http://alexandre.alapetite.fr/doc-alex/html5-webcam/index2.en.html
That I cannot stop the video once I start it. I'm using OS X 10.8.1 and the latest nightly 08/29/12.
I can also confirm that Chrome works properly using the same link.
Fixed by the patch in bug 784829.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•