This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Looks like it might be the same underlying cause as  Issue 760035 .

At a peek, is it safe to assign the result of std::round to an int, and then use that?
 Please take a look, thanks.

ClusterFuzz has detected this issue as fixed in range 498140:498349.

Detailed report: https://clusterfuzz.com/testcase?key=5162886766002176

Fuzzer: inferno_flicker
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Global-buffer-overflow READ 4
Crash Address: 0x61d2a924
Crash State:
  media::VideoDecodeStatsReporter::GetFpsBucket
  media::VideoDecodeStatsReporter::UpdateFrameRateStability
  media::VideoDecodeStatsReporter::UpdateStats
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=497874:497956
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=498140:498349

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5162886766002176

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot