Open
Bug 797423
Opened 13 years ago
Updated 3 years ago
Add thread safety asserts throughout TransportLayer
Categories
(Core :: WebRTC: Networking, defect, P4)
Tracking
()
NEW
| backlog | webrtc/webaudio+ |
People
(Reporter: ekr, Unassigned)
Details
TransportLayer is generally not thread safe. We should addd asserts to make sure it is used correctly.
|
||
Updated•13 years ago
|
Whiteboard: [WebRTC], [blocking-webrtc+]
|
||
Comment 1•13 years ago
|
||
Yes, we should but it does not block
Priority: -- → P2
Whiteboard: [WebRTC], [blocking-webrtc+] → [WebRTC], [blocking-webrtc-]
|
||
Updated•10 years ago
|
backlog: --- → webRTC+
Rank: 25
Whiteboard: [WebRTC], [blocking-webrtc-]
|
||
Updated•10 years ago
|
Rank: 25 → 35
Priority: P2 → P3
|
||
Comment 2•8 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•