822204 - WebRTC networking keeps going after closing/reloading the tab

Status: VERIFIED FIXED

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

Description

[Martin Storsjö]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17

Steps to reproduce:

Try to establish a PeerConnection to a peer (non-browser test implementation). The non-browser peer succeeds doing the STUN handshake, but doesn't respond go the DTLS ClientHello packets.

Alternatively, open the self-connection test page at http://mozilla.github.com/webrtc-landing/pc_test.html, start the connection, then close the tab.


Actual results:

After closing/reloading the tab, the browser still sends new ClientHello packets to the peer about every 60 seconds.

For the self-connection test page, after closing it, the browser still sends RTCP RR packets (about 1 per second) after closing the page.

Additionally (possibly unrelated), occasionally the browser is seen sending 1-byte UDP packets on localhost, to/from port 52904 every time.


These issues have been reproduced with the latest FirefoxNightly build, 20.0a1 (2012-12-16).


Expected results:

The browser should stop interacting with the peer when the tab containing the PeerConnection objects is closed/reloaded.

Comment 1

[Martin Storsjö]

The issues about packets on port 52904 turned out to be unrelated, but the rest of the issues mentioned still apply.

Comment 2

[Maire Reavy [:mreavy]]

We believe this is fixed with the current Nightly.  Can you please retest?  Thanks!

Comment 3

[Martin Storsjö]

Yes, I can confirm that this is fixed in the latest nightly now. Thanks for the quick response!

Comment 4

[Jason Smith [:jsmith]]

Marking as verified per comment 3