Closed Bug 811011 Opened 12 years ago Closed 12 years ago

gUM - Trying to request audio off of one device, stopping the audio, then requesting audio on a different device - audio stream does not start up

Categories

(Core :: WebRTC: Audio/Video, defect, P1)

defect

Tracking

()

RESOLVED DUPLICATE of bug 811695

People

(Reporter: jsmith, Unassigned)

References

Details

(Whiteboard: [getUserMedia][blocking-gum+])

Steps:

1. Go to https://people.mozilla.com/~anarayanan/webrtc/gum_test.html with a USB mic headset and a internal mic setup
2. Request audio with your internal mic
3. Select stop after the audio stream starts playing
4. Request audio again with your USB headset

Expected:

The audio stream should start using your USB headset as the mic.

Actual:

The audio stream does not start. Killing the tab, reloading the page, or even opening up a new page with the contents to request audio off of the USB headset will continue to fail. The only work-around is to restart your browser to be able to use the other input audio source.
Verified on Nightly Win32; building a debug build to test.
Version: unspecified → Trunk
Priority: -- → P1
Whiteboard: [getUserMedia][blocking-gum+]
The problem here is the 127.0.0.1 socket that gets reused.  Solved by getting rid of the socket in bug 811695
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.