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

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

Automatically adding ccs based on suspected regression changelists:

Fix main thread top controls scrolling to mirror CC. by bokan@chromium.org - https://chromium.googlesource.com/chromium/src/+/c63441cc9941c223e2f2d311085903c00da85938

Make sure TestRunner::topLoadingFrame is from the main test window. by lukasza@chromium.org - https://chromium.googlesource.com/chromium/src/+/8973c521e42739f6c2d1e1b3c8fa7c6e90753014

Make WebWidget::resize early out if the size doesn't change. by bokan@chromium.org - https://chromium.googlesource.com/chromium/src/+/71cb5b185f274ee0f96b346ce8a515073e9e2975

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

My attempt to repro locally failed because of issue 751218.

I (for now) have a Trusty CloudTop VM so I'll try to repro this week.

I can remove the security flags from this, right? There is only test code on the call stack.

RE: #c7: yes

 Issue 821258  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 545714:545715.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  test_runner::TestRunnerForSpecificView::Reset
  test_runner::WebViewTestProxyBase::Reset
  test_runner::TestInterfaces::ResetAll
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=389884:390115
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=545714:545715

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

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

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