Open Bug 827982 Opened 12 years ago Updated 11 months ago

ICE socket exhaustion should return a better error code

Categories

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

Product:
Core
Component:
WebRTC: Networking
Version:
21 Branch
Type:
defect

Tracking

()

Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: abr, Unassigned)

References

Details

Currently, when the ICE layer cannot allocate a new socket to do its job, it returns NS_ERROR_NOT_AVAILABLE (0x80040111), which isn't very useful in figuring out what has gone wrong (cf. Bug 824919). Ideally, it should return something more specific, like NS_ERROR_SOCKET_CREATE_FAILED (0x804B0034).
Assignee: adam → ekr
backlog: --- → webRTC+
Rank: 35
Whiteboard: [WebRTC] [blocking-webrtc-]
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4

Sorry, there was a problem with the detection of inactive users. I'm reverting the change.

Assignee: nobody → ekr
Severity: normal → S3

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Assignee: ekr → nobody
You need to log in before you can comment on or make changes to this bug.