Mismatching RIDs and encodings result in release assertion

RESOLVED WORKSFORME

Status

()

Core
WebRTC: Signaling
P2
normal
Rank:
19
RESOLVED WORKSFORME
a year ago
5 months ago

People

(Reporter: drno, Unassigned)

Tracking

({stale-bug})

Trunk
stale-bug
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

a year ago
Created attachment 8873678 [details]
test3.html

We have no code which filters out non-matching encondings and/or RIDs. Attached is a test case which demonstrates the problem.
(Reporter)

Updated

a year ago
Rank: 19
This is a P1 bug without an assignee. 

P1 are bugs which are being worked on for the current release cycle/iteration/sprint. 

If the bug is not assigned by Monday, 28 August, the bug's priority will be reset to '--'.
Keywords: stale-bug
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
Attachment seems to work fine. Didn't we fix this in another bug?
Flags: needinfo?(drno)
(Reporter)

Comment 4

5 months ago
Back then we did this the other half of the equation over in bug 1367930. But I opened this one, because we didn't fix this part yet.

I don't recall any other fixes in that area. But if it doesn't assert any more we can probably close this here.
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Flags: needinfo?(drno)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.