frame_id is unwraped from a 16bit value.
Getting to int64_t boundaries would take more than 2^48 packets.
That scenario considered unrealistic and thus untested.
Bug: chromium:1053482
Change-Id: Ib3f52d4528b20915b2330773f616d9304f45cac6
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/168682
Reviewed-by: Sam Zackrisson <saza@webrtc.org>
Commit-Queue: Danil Chapovalov <danilchap@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#30607}
97b59f060c