Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

> Predator was unable to identify any culprit changelists for this test case. 

> Unable to find actual suspect through code search and also observing no possible suspect CL under regression range, hence cc'ing to the file owner as per below link
https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/media_controls/OWNERS?sq=package:chromium&dr

Thanks!

ClusterFuzz has detected this issue as fixed in range 565324:565325.

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

Fuzzer: ochang_search_index_mutator
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  blink::MediaControlTimeDisplayElement::FormatTime
  blink::MediaControlRemainingTimeDisplayElement::FormatTime
  blink::MediaControlTimeDisplayElement::SetCurrentValue
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=552707:552711
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=565324:565325

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

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.

ClusterFuzz testcase 5214253330726912 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.