Open
Bug 1155017
Opened 10 years ago
Updated 2 years ago
Saved statistics for closed PeerConnections are lost when the last content tab is closed in e10s
Categories
(Core :: WebRTC: Signaling, defect, P4)
Tracking
()
NEW
mozilla39
Tracking | Status | |
---|---|---|
e10s | + | --- |
backlog | webrtc/webaudio+ |
People
(Reporter: pkerr, Unassigned)
References
Details
About:webrtc runs in the chrome process and displays data for both live and previously active but now closed PeerConnections. The data for the closed PeerConnections is stored in the PeerConnectionCtx instance which is a per-process singleton. When the last content tab is closed, the PeerConnectionCtx instance associated with the content process is destroyed. After that point, only closed connection data from the chrome process PeerConnectionCtx instance is available. (The same applied to the ICE connection logs.)
The storage of statistics for the closed PeerConnections should be moved to the WebrtcGlobalInformation instance in the chrome process.
![]() |
||
Updated•10 years ago
|
tracking-e10s:
--- → +
Updated•10 years ago
|
backlog: --- → webRTC+
Rank: 35
Priority: P2 → P3
Comment 1•7 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•