Closed Bug 1272588 Opened 8 years ago Closed 2 years ago

Unplugging a device for an active gUM capture doesn't end the track

Categories

(Core :: Audio/Video: MediaStreamGraph, defect, P3)

48 Branch
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: pehrsons, Unassigned)

References

Details

Unplugging an audio device that is being captured should result in a stop of capture and the MediaStreamTrack ending.

Currently we fail over to another device (which one?) instead of ending the capture.

It's unclear what happens when we unplug the last device available to the system.
When we fail over to another device in this manner, do we do so without another gUM prompt? Because if we do, that would be pretty bad, and would probably justify a higher priority.
backlog: --- → webrtc/webaudio+
Rank: 35
Flags: needinfo?(pehrsons)
Priority: -- → P3
We do, yeah.
Flags: needinfo?(pehrsons)
Yikes. What's the worst that could happen?
Rank: 35 → 15
Priority: P3 → P1
I tried to reproduce this but ran into bug 1272392 and bug 1272386 instead, one for each camera I have :-/

Can anyone other than Andreas reproduce this? I'm curious since this seems like a not so well tested area with lots of varying symptoms.
See Also: → 1272392
I reproduced that with the patches from bug 1208373 and I got the described behavior. I use Plantronics Audio648 usb.
Rank: 15 → 22
Priority: P1 → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3

Seems overtaken by events.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.