Closed Bug 2015211 Opened 7 months ago Closed 7 months ago

Add logging to JsepTrack

Categories

(Core :: WebRTC: Signaling, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
149 Branch
Tracking Status
firefox-esr140 --- fixed
firefox149 --- fixed

People

(Reporter: ng, Assigned: ng)

References

Details

Attachments

(1 file)

Adding jsep debug logging to JsepTrack.

Let's get ahead of the upcoming changes to the assert guidance and
start logging everywhere we are asserting. We can use this logging
to guide the discussion on which of these functions to make failable.

We should also do this for JsepSessionImpl, etc.

Assignee: nobody → ngrunbaum
Status: NEW → ASSIGNED
See Also: → CVE-2026-4718
Status: ASSIGNED → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
Target Milestone: --- → 149 Branch
See Also: CVE-2026-4718 →
QA Whiteboard: [qa-triage-done-c150/b149]

Comment on attachment 9544354 [details]
Bug 2015211 - add logging to jseptrack;r=bwc

ESR Uplift Approval Request

  • If this is not a sec:{high,crit} bug, please state case for ESR consideration: Improved debugging of WebRTC negotiation failures.
  • User impact if declined: Greater difficulty in diagnosing WebRTC negotiation failures.
  • Fix Landed on Version: 149
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): This is a logging improvement that doesn't change behavior
Attachment #9544354 - Flags: approval-mozilla-esr140?

Nico, your patch does not apply cleanly to the esr140 branch, could you rebase it please? Thanks

Flags: needinfo?(ngrunbaum)

Comment on attachment 9544354 [details]
Bug 2015211 - add logging to jseptrack;r=bwc

Approved for 140.9esr.

Flags: needinfo?(ngrunbaum)
Attachment #9544354 - Flags: approval-mozilla-esr140? → approval-mozilla-esr140+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: