Closed Bug 1354869 Opened 7 years ago Closed 7 years ago

RTCPeerConnection constructor throw if network is down

Categories

(Core :: WebRTC: Networking, defect)

52 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 831926

People

(Reporter: shaharmor1, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce:

1. Disconnect from the internet
2. Run this in the console: "var connection = new RTCPeerConnection()"


Actual results:

InvalidStateError is thrown: "Can't create RTCPeerConnections when the network is down"


Expected results:

An error should not be thrown.
Component: Untriaged → WebRTC
Product: Firefox → Core
In 52 this fails as described above but in nightly this seems to work. Nils, do you know if 831926 was resolved in another bug?
Flags: needinfo?(drno)
See Also: → 831926
Component: WebRTC → WebRTC: Networking
(In reply to Nico Grunbaum [:ng] from comment #1)
> In 52 this fails as described above but in nightly this seems to work. Nils,
> do you know if 831926 was resolved in another bug?

No none of the code around that has changed.

But you might have tested different scenario. Here is what I found:

- without e10s I always get the network state error
- with e10s:
  - if I first select "work offline" and then open the console to paste the code I get no error
  - if I first open the console, then select "work offline" and then paste the code I get again the error

So not getting the error message is basically some kind of bug in the code which currently still prevents you from using PeerConnections w/o network.

I think this is basically a dupe of bug 831926.
Flags: needinfo?(drno)
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.