Closed Bug 1491730 Opened 6 years ago Closed 6 years ago

the rtp is still sent to remove even disable the videotrack

Categories

(Core :: WebRTC: Networking, defect)

62 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: xpeng, Unassigned, NeedInfo)

Details

(Whiteboard: [needinfo reporter 2018/10/01])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 Build ID: 20180830143136 Steps to reproduce: 1.start screen sharing with webrtc 2.set the videotrack.enabled to false 3.there is rtp packets sent to remote (it's not packets for keepalive ) Actual results: there is rtp packets sent to remote , but it's normal for chrome Expected results: there is no rtp packets sent to remote (except the packet for keepalive)
Component: Untriaged → WebRTC: Networking
Product: Firefox → Core
ni? Jan-Ivar since I'm not sure how to triage this
Flags: needinfo?(jib)
Hi xpeng, thanks for filing! We need more information to narrow this down: (In reply to xpeng from comment #0) > Expected results: > > there is no rtp packets sent to remote (except the packet for keepalive) This matches what I'm seeing in Firefox 62 on OSX with https://jsfiddle.net/jib1/2bk4ednj/ Speed: 24 packets/s (26851 bytes/s) ...and when I mute (set track.disabled = true): Speed: 1 packets/s (235 bytes/s) This is expected, as we send one frame per second, as the spec recommends [1] (is this what you call "keepalive"?) > Actual results: > > there is rtp packets sent to remote , but it's normal for chrome I can't reproduce. Can you try the fiddle above and tell me if you're still seeing the problem? On what platform? I'm also confused by your statement on Chrome. In Chrome I get: Speed: 203 packets/s (221203 bytes/s) ...and when I mute: Speed: 31 packets/s (3831 bytes/s) I.e. it seems Chrome sends more packets (and bytes) on mute than Firefox. Does this match what you see? [1] http://w3c.github.io/webrtc-pc/#dom-rtcrtpsender-track says "if the track's output is disabled [...] In the case of video, the RTCRtpSender SHOULD send one black frame per second."
Flags: needinfo?(jib) → needinfo?(xpeng)
Whiteboard: [needinfo reporter 2018/10/01]

2019-03-06

This bug is part of a group of bugs which have had an open needinfo for at least 12 weeks.

The request for information has not been answered, and we can't move forward on the bug so we are closing it.

If the defect is still present, please reopen this bug with an updated report.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.