Closed Bug 788183 Opened 12 years ago Closed 2 years ago

[meta] Investigate end-to-end latency issues in WebRTC

Categories

(Core :: WebRTC, defect)

Product:
Core
Component:
WebRTC
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: jesup, Unassigned)

References

Details

(Keywords: meta) 

Investigate end-to-end latency issues in WebRTC.  This is everything from GetUserMedia() to transport and jitter issues to MediaStream buffering and clock drift (if it causes latency buildup; there are other issues with drift like sync).

Need instrumentation (probably on this bug) and detailed looks at some subsystems (probably bugs this will depend on, like the audio driver latency bug 694815).

Preferably this will turn into something that can be looked at live or after-the-fact, and also used in unit and talos tests.
Whiteboard: [getUserMedia]
Whiteboard: [getUserMedia] → [getUserMedia], [WebRTC], [blocking-gum-], [blocking-webrtc-]
Depends on: 920325
Depends on: 920328
Depends on: 920329
Keywords: meta
Whiteboard: [getUserMedia], [WebRTC], [blocking-gum-], [blocking-webrtc-]
Summary: Investigate end-to-end latency issues in WebRTC → [meta] Investigate end-to-end latency issues in WebRTC
Assignee: rjesup → nobody
QA Contact: jsmith

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: critical → --

Old meta bug with empty dependency tree. Closing.

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