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 and CL could not provide any possible suspects.
Using the code search for the file, “base_rendering_context_2d.cc” assigning to concern owner from GIT revision log.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/04ed6e6eff3c79d66517f2f25eb36d01318d4885

@xidachen -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 555317:555318.

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

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  blink::BaseRenderingContext2D::DrawImageInternal
  Draw<
  blink::BaseRenderingContext2D::drawImage
  
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=555317:555318

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

Additional requirements: Requires HTTP

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.