Closed Bug 798797 Opened 12 years ago Closed 7 years ago

Remove MOZ_CRASH for exporter failure

Categories

(Core :: WebRTC: Networking, defect, P3)

Product:
Core
Component:
WebRTC: Networking
Platform:
x86
macOS
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: ekr, Unassigned)

Details

Currently if the TLS exporter call in MediaPipeline.cpp fails, we call MOZ_CRASH. This is there because if you try to run the exporter in the wrong TLS state it will fail and leave you with garbage in the buffer. This should never happen but the TLS logic is complicated ws te so we want to know if it does. Remove this once we have enough field experience to downgrade to a runtime error.
Whiteboard: [WebRTC] [blocking-webrtc-]
Can we downgrade this now?
Flags: needinfo?(ekr)
Yes, I think this is safe.
Flags: needinfo?(ekr)
Can we resolve this, or decide to leave the MOZ_CRASH?
backlog: --- → webRTC+
Rank: 25
Flags: needinfo?(rjesup)
Priority: -- → P2
Whiteboard: [WebRTC] [blocking-webrtc-]
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Removing this in one of the patches on bug 1455647.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Flags: needinfo?(rjesup)
You need to log in before you can comment on or make changes to this bug.