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

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

Probably this one?
https://chromium-review.googlesource.com/c/chromium/src/+/923427

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

commit 72599b86937978b14b7992e25c0462373d0c5515
Author: Stefan Zager <szager@chromium.org>
Date: Mon Jun 25 21:08:25 2018

Don't overflow EmbeddedContentView frame rect.

This extends to the other EmbeddedContentView subclasses the same fix
as was made to LocalFrameView in:

https://chromium-review.googlesource.com/1055675

BUG= 855950 
R=skobes@chromium.org

Change-Id: I4c9f29fc1e04213ff22e5debd9630ebb81eb1812
Reviewed-on: https://chromium-review.googlesource.com/1114071
Commit-Queue: Stefan Zager <szager@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570180}
[modify] https://crrev.com/72599b86937978b14b7992e25c0462373d0c5515/third_party/blink/renderer/core/exported/web_plugin_container_impl.cc
[modify] https://crrev.com/72599b86937978b14b7992e25c0462373d0c5515/third_party/blink/renderer/core/frame/remote_frame_view.cc

ClusterFuzz has detected this issue as fixed in range 570179:570182.

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

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

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  blink::IntPoint::Move
  blink::WebPluginContainerImpl::FrameRect
  blink::WebPluginContainerImpl::ComputeClipRectsForPlugin
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=549059:549062
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=570179:570182

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

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

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