Merge 60: Handle zero timestamp in RTCVideoEncoder timestamp matching & add UMA

Merge 60: Handle zero timestamp in RTCVideoEncoder timestamp matching & add UMA

Desktop/tab capture can send zero as the first frame's capture timestamp. This CL
changes treating zero as the default timestamp to handle those cases.

If a platform doesn't preserve and return 0 as the timestamp, i.e. Android, the first
frame will be matched and calculated correctly. However, second value(which is
nonzero) will fail to match and stop.

Additionally, this CL adds a UMA to track the platforms and cases where this might
fail.

BUG=732552
TEST=Observed chrome://webrtc-internals metrics on guado using Hangouts
screenshare.

Review-Url: https://codereview.chromium.org/2933213003
Cr-Original-Commit-Position: refs/heads/master@{#479097}
Review-Url: https://codereview.chromium.org/2948623002
Cr-Commit-Position: refs/branch-heads/3112@{#389}
Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}
Committed: https://chromium.googlesource.com/chromium/src/+/16d0a3e701da48ea0e6a1f5b171f6f000bff6993

[emircan, 2017-06-19 19:02:31]

Description was changed from

==========
Handle zero timestamp in RTCVideoEncoder timestamp matching & add UMA

Desktop/tab capture can send zero as the first frame's capture timestamp. This
CL
changes treating zero as the default timestamp to handle those cases.

If a platform doesn't preserve and return 0 as the timestamp, i.e. Android, the
first
frame will be matched and calculated correctly. However, second value(which is
nonzero) will fail to match and stop.

Additionally, this CL adds a UMA to track the platforms and cases where this
might
fail.

BUG=732552
TEST=Observed chrome://webrtc-internals metrics on guado using Hangouts
screenshare.

Review-Url: https://codereview.chromium.org/2933213003
Cr-Commit-Position: refs/heads/master@{#479097}
(cherry picked from commit 115c560f5886afd3c512d054c988439893974f24)
==========

to

==========
Merge 60: Handle zero timestamp in RTCVideoEncoder timestamp matching & add UMA

Desktop/tab capture can send zero as the first frame's capture timestamp. This
CL
changes treating zero as the default timestamp to handle those cases.

If a platform doesn't preserve and return 0 as the timestamp, i.e. Android, the
first
frame will be matched and calculated correctly. However, second value(which is
nonzero) will fail to match and stop.

Additionally, this CL adds a UMA to track the platforms and cases where this
might
fail.

BUG=732552
TEST=Observed chrome://webrtc-internals metrics on guado using Hangouts
screenshare.

Review-Url: https://codereview.chromium.org/2933213003
Cr-Commit-Position: refs/heads/master@{#479097}
(cherry picked from commit 115c560f5886afd3c512d054c988439893974f24)
==========

[emircan, 2017-06-19 19:03:36]

Description was changed from

==========
Merge 60: Handle zero timestamp in RTCVideoEncoder timestamp matching & add UMA

Desktop/tab capture can send zero as the first frame's capture timestamp. This
CL
changes treating zero as the default timestamp to handle those cases.

If a platform doesn't preserve and return 0 as the timestamp, i.e. Android, the
first
frame will be matched and calculated correctly. However, second value(which is
nonzero) will fail to match and stop.

Additionally, this CL adds a UMA to track the platforms and cases where this
might
fail.

BUG=732552
TEST=Observed chrome://webrtc-internals metrics on guado using Hangouts
screenshare.

Review-Url: https://codereview.chromium.org/2933213003
Cr-Commit-Position: refs/heads/master@{#479097}
(cherry picked from commit 115c560f5886afd3c512d054c988439893974f24)
==========

to

==========
Merge 60: Handle zero timestamp in RTCVideoEncoder timestamp matching & add UMA

Desktop/tab capture can send zero as the first frame's capture timestamp. This
CL
changes treating zero as the default timestamp to handle those cases.

If a platform doesn't preserve and return 0 as the timestamp, i.e. Android, the
first
frame will be matched and calculated correctly. However, second value(which is
nonzero) will fail to match and stop.

Additionally, this CL adds a UMA to track the platforms and cases where this
might
fail.

BUG=732552
TEST=Observed chrome://webrtc-internals metrics on guado using Hangouts
screenshare.

Review-Url: https://codereview.chromium.org/2933213003
Cr-Commit-Position: refs/heads/master@{#479097}
(cherry picked from commit 115c560f5886afd3c512d054c988439893974f24)
NOTRY=true
NOPRESUBMIT=true
TBR=pbos@chromium.org,asvitkine@chromium.org
==========

[emircan, 2017-06-19 19:03:57]

The CQ bit was checked by emircan@chromium.org

[commit-bot: I haz the power, 2017-06-19 19:04:33]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-06-19 19:35:13]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1497899037352280, "parent_rev":
"43f681168833ed6399c4cb17a8c9bfed413712e7", "commit_rev":
"16d0a3e701da48ea0e6a1f5b171f6f000bff6993"}

[commit-bot: I haz the power, 2017-06-19 19:35:25]

Description was changed from

==========
Merge 60: Handle zero timestamp in RTCVideoEncoder timestamp matching & add UMA

Desktop/tab capture can send zero as the first frame's capture timestamp. This
CL
changes treating zero as the default timestamp to handle those cases.

If a platform doesn't preserve and return 0 as the timestamp, i.e. Android, the
first
frame will be matched and calculated correctly. However, second value(which is
nonzero) will fail to match and stop.

Additionally, this CL adds a UMA to track the platforms and cases where this
might
fail.

BUG=732552
TEST=Observed chrome://webrtc-internals metrics on guado using Hangouts
screenshare.

Review-Url: https://codereview.chromium.org/2933213003
Cr-Commit-Position: refs/heads/master@{#479097}
(cherry picked from commit 115c560f5886afd3c512d054c988439893974f24)
NOTRY=true
NOPRESUBMIT=true
TBR=pbos@chromium.org,asvitkine@chromium.org
==========

to

==========
Merge 60: Handle zero timestamp in RTCVideoEncoder timestamp matching & add UMA

Desktop/tab capture can send zero as the first frame's capture timestamp. This
CL
changes treating zero as the default timestamp to handle those cases.

If a platform doesn't preserve and return 0 as the timestamp, i.e. Android, the
first
frame will be matched and calculated correctly. However, second value(which is
nonzero) will fail to match and stop.

Additionally, this CL adds a UMA to track the platforms and cases where this
might
fail.

BUG=732552
TEST=Observed chrome://webrtc-internals metrics on guado using Hangouts
screenshare.

Review-Url: https://codereview.chromium.org/2933213003
Cr-Original-Commit-Position: refs/heads/master@{#479097}
Review-Url: https://codereview.chromium.org/2948623002
Cr-Commit-Position: refs/branch-heads/3112@{#389}
Cr-Branched-From:
b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}
Committed:
https://chromium.googlesource.com/chromium/src/+/16d0a3e701da48ea0e6a1f5b171f...
==========

[commit-bot: I haz the power, 2017-06-19 19:35:27]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/16d0a3e701da48ea0e6a1f5b171f...