Open Bug 1765437 Opened 3 years ago Updated 3 years ago

We need proper error handling in our fingerprint calculation code

Categories

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

Product:
Core
Component:
WebRTC: Signaling
Type:
defect

Tracking

()

People

(Reporter: bwc, Unassigned)

Details

If this code fails, we set mCertificate to nullptr, which will just crash the process if JS tries to access the fingerprint or certificate. We need to be handling and surfacing these errors properly.

Note: It is not clear to me that this code ever fails in practice, but we do need to do the right thing if it does.

Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.