Closed
Bug 952241
Opened 12 years ago
Closed 12 years ago
Ending an audio P2P call with B2G --> Desktop on the same wifi network still shows high network activity present on FxOS
Categories
(Core :: WebRTC: Networking, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: jsmith, Unassigned)
Details
Build - 12/19/2013 Leo 1.4
STR
1. Go to http://mysecondwebrtc.appspot.com/ on Desktop Firefox Beta (Gecko 27) on low activity wifi network
2. Go to http://mysecondwebrtc.appspot.com/ on FxOS 1.4 (Gecko 29) on same wifi network as [1]
3. Request access & grant access to your mic on Desktop Firefox & FxOS
4. Register the remote client ID on FxOS
5. Talk on your FxOS mic for about 30 seconds to the Desktop machine
6. Close the Desktop Firefox tab running http://mysecondwebrtc.appspot.com/
Expected
Network activity should stop quickly on FxOS, as the call as ended.
Actual
Network activity continues to be present on FxOS at a high rate. I'm wondering if this is an indicator that the call wasn't really closed on the FxOS side when the Desktop Firefox client left.
![]() |
Reporter | |
Updated•12 years ago
|
Blocks: b2g-webrtc
![]() |
Reporter | |
Comment 1•12 years ago
|
||
Ran this for a while after the remote peer closed - it looks like the network activity infinitely runs at this point.
![]() |
Reporter | |
Comment 2•12 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #1)
> Ran this for a while after the remote peer closed - it looks like the
> network activity infinitely runs at this point.
Also happens on FxAndroid --> B2G call.
![]() |
Reporter | |
Comment 3•12 years ago
|
||
Per the discussion in webrtc b2g meeting in Dec - this is expected because the developer hasn't closed the connection, so network activity would still be present. A bug would be present here only if this happened after we closed the connection. So we're doing the right behavior here.
You need to log in
before you can comment on or make changes to this bug.
Description
•