Open Bug 1624053 Opened 6 years ago Updated 3 years ago

Consider retrying camera/mic on AbortError/NotReadableError 200 ms after recent device stop

Categories

(Core :: WebRTC: Audio/Video, enhancement, P3)

Product:
Core
Component:
WebRTC: Audio/Video
Platform:
Unspecified
All
Type:
enhancement

Tracking

()

People

(Reporter: jib, Unassigned)

References

(Blocks 1 open bug)

Details

+++ This bug was initially created as a clone of Bug #1624002 +++

We have a couple of bugs filed where getUserMedia is failing if invoked immediately after a track.stop() on systems that cannot open more than one device of a kind at a time.

We've seen it with Android camera in bug 1624002, and we see it with Firefox's current inherent limit of only one open microphone at a time.

We might be able to solve many of these centrally in MediaManager with a simple policy of detecting these failures in getUserMedia and trying again after ~200 ms before giving up and rejecting the promise.

If we want to optimize, we could even get fancy and only do this if we know track.stop() was called recently.

Blocks: 1624002
No longer depends on: 1624002
Type: defect → enhancement
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.