Bug 172682 - framesPerSecond is always 0 in RTCStats
Summary: framesPerSecond is always 0 in RTCStats
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2017-05-27 08:04 PDT by Michael Leaney
Modified: 2017-05-30 00:08 PDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Leaney 2017-05-27 08:04:51 PDT 
framesPerSecond is always 0 in RTCStats obtained from calling getStats on a peer connection. This is observed in the latest nightly of WebKit.

Steps to Reproduce:
Head to: https://webrtc.github.io/samples/src/content/peerconnection/constraints/
Click "Get media"
Click "Connect"
Observe the framesPerSecond is 0 for the remote video track stats

Expected Results:
The framesPerSecond matches the actual frame rate of the video

Observed Results:
The framesPerSecond is always 0
Comment 1 Radar WebKit Bug Importer 2017-05-27 10:00:33 PDT 
<rdar://problem/32442992>
Comment 2 Jon Lee 2017-05-28 19:26:28 PDT 
rdar://problem/32368139