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 Code Search for the file, "autofill_handler.cc" and observed there was some recent changes for the below file.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/a674b1ddd40462bb41eef50f0befc6000d56c393

michaelbai@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e202adab6d3ba9e97f27fbc78ab218481af93a0c

commit e202adab6d3ba9e97f27fbc78ab218481af93a0c
Author: Tao Bai <michaelbai@chromium.org>
Date: Wed Feb 14 02:07:14 2018

Using float in ContentAutofillDriver::TransformBoundingBoxToViewportCoordinates

BUG= 807531 

Change-Id: Ic86c3b3bd03e2e056c8eb56d3836d025360e620a
Reviewed-on: https://chromium-review.googlesource.com/910041
Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Commit-Queue: Tao Bai <michaelbai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536604}
[modify] https://crrev.com/e202adab6d3ba9e97f27fbc78ab218481af93a0c/components/autofill/content/browser/content_autofill_driver.cc

ClusterFuzz has detected this issue as fixed in range 536603:536604.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  autofill::ContentAutofillDriver::TransformBoundingBoxToViewportCoordinates
  autofill::AutofillHandler::OnFocusOnFormField
  autofill::mojom::AutofillDriverStubDispatch::Accept
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=531626:531630
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=536603:536604

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

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 4981644185042944 is verified as fixed, so closing issue as verified.

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