Open Bug 1328531 Opened 7 years ago Updated 2 years ago

Investigate the high amount of WEBRTC_CALL_TYPE 0 in Telemetry

Categories

(Core :: WebRTC, defect, P3)

Product:
Core
Component:
WebRTC
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox53 --- affected
Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: drno, Unassigned)

References

(Blocks 1 open bug)

Details

WEBRTC_CALL_TYPE = 0 means a PeerConnection got closed which never had an audio or video track or a data channel in it.

Is our telemetry call faulty here?

The other possibility is that this reports empty PeerConnection which were called for tracking purposes (?). The fact that the call type gets reported no matter which signaling state the PC ever reached hints to this IMHO.
backlog: --- → webrtc/webaudio+
Rank: 29
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Depends on: webrtc-telemetry
Blocks: webrtc-telemetry
No longer depends on: webrtc-telemetry
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.