Closed Bug 864117 Opened 13 years ago Closed 11 years ago

CreateOffer() with no network connection never succeeds or fails

Categories

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

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: jsmith, Unassigned)

Details

Attachments

(3 files)

Attached file Test Case
Note: No network connection = wireless is disconnected. This will not reproduce with "work offline" in Firefox. STR: 1. Load the attached test case without a network connection 2. Check console Expected: We should get a NS_ERROR_FAILURE indicating that you can't create a peer connection without a network connection. Actual: The peer connection is successfully created. We'll fail silently when we reach createOffer, so the developer never knows the connection failed.
Whiteboard: [WebRTC][blocking-webrtc-][turn]
Why is this marked as TURN? Does it succeed without TURN?
(In reply to Eric Rescorla (:ekr) from comment #1) > Why is this marked as TURN? Does it succeed without TURN? Fails on STUN too.
Summary: [TURN] Trying to create a peer connection without a network connection is successful, but it shouldn't be → Trying to create a peer connection without a network connection is successful, but it shouldn't be
Whiteboard: [WebRTC][blocking-webrtc-][turn] → [WebRTC][blocking-webrtc-]
You should be able to create a PeerConnection without a network connection, so that part is incorrect. CreateOffer (I believe) should eventually time out and return an error if it can't even get local interface IP addresses. If it never does, that's probably an error. Please do a run with signaling:5,mtransport:5 logging and upload it (my laptop has a VM that looks like a network interface on it, so it's hard for me to test, and my linux machine normally doesn't have a keyboard or mouse - perhaps I'll just plug some in and try there.)
Summary: Trying to create a peer connection without a network connection is successful, but it shouldn't be → CreateOffer() with no network connection never succeeds or fails
(In reply to Randell Jesup [:jesup] from comment #3) > You should be able to create a PeerConnection without a network connection, > so that part is incorrect. > > CreateOffer (I believe) should eventually time out and return an error if it > can't even get local interface IP addresses. If it never does, that's > probably an error. > > Please do a run with signaling:5,mtransport:5 logging and upload it (my > laptop has a VM that looks like a network interface on it, so it's hard for > me to test, and my linux machine normally doesn't have a keyboard or mouse - > perhaps I'll just plug some in and try there.) Yes, this is bug 827982... unfortunately, the writeup isn't accurate any more because we now have asynchronous StartGathering.
Attached file Signalling Log
Not sure if it is still necessary, but here's the logs as requested as I discovered this the other day.
Attached file Alternate test case
The test case I was using (just in case).
may well be fixed now...
backlog: --- → webRTC+
Rank: 55
Priority: -- → P5
Whiteboard: [WebRTC][blocking-webrtc-]
Just tested, seems to work.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: