Bug 172682

Summary:	framesPerSecond is always 0 in RTCStats
Product:	WebKit	Reporter:	Michael Leaney <mleaney>
Component:	Media	Assignee:	Nobody <webkit-unassigned>
Status:	NEW
Severity:	Normal	CC:	adam, eric.carlson, jonlee, webkit-bug-importer, youennf
Priority:	P2	Keywords:	InRadar
Version:	WebKit Nightly Build
Hardware:	Unspecified
OS:	Unspecified

Michael Leaney

Reported 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

Attachments
Add attachment proposed patch, testcase, etc.

Radar WebKit Bug Importer

Comment 1 2017-05-27 10:00:33 PDT

<rdar://problem/32442992>

Jon Lee

Comment 2 2017-05-28 19:26:28 PDT

rdar://problem/32368139

Note You need to log in before you can comment on or make changes to this bug.