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

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

mmoroz, mbarbella: Is this a test harness bug?

Seems likely, yeah.

Okay I am kicking it out of the security queue for now, I am not sure to where it should be triaged.

Automatically adding ccs based on suspected regression changelists:

https://chromium.googlesource.com/chromium/src/+/16289b3ef759d892a4058671e0657c016101be23 (Use C++11 alignment primitives by brettw@chromium.org)https://chromium.googlesource.com/chromium/src/+/478c83ce79be0f8f41911bfb41840156af6d8a68 (LayoutTests, devtools: allow creating and testing OOPIFs. by pfeldman@chromium.org)
If this is incorrect, please apply the Test-Predator-Wrong-CLs label.

Automatically adding ccs based on suspected regression changelists:

https://chromium.googlesource.com/chromium/src/+/16289b3ef759d892a4058671e0657c016101be23 (Use C++11 alignment primitives by brettw@chromium.org)https://chromium.googlesource.com/chromium/src/+/478c83ce79be0f8f41911bfb41840156af6d8a68 (LayoutTests, devtools: allow creating and testing OOPIFs. by pfeldman@chromium.org)
If this is incorrect, please apply the Test-Predator-Wrong-CLs label.

Automatically adding ccs based on suspected regression changelists:

https://chromium.googlesource.com/chromium/src/+/16289b3ef759d892a4058671e0657c016101be23 (Use C++11 alignment primitives by brettw@chromium.org)https://chromium.googlesource.com/chromium/src/+/478c83ce79be0f8f41911bfb41840156af6d8a68 (LayoutTests, devtools: allow creating and testing OOPIFs. by pfeldman@chromium.org)
If this is incorrect, please apply the Test-Predator-Wrong-CLs label.

Automatically adding ccs based on suspected regression changelists:

https://chromium.googlesource.com/chromium/src/+/16289b3ef759d892a4058671e0657c016101be23 (Use C++11 alignment primitives by brettw@chromium.org)https://chromium.googlesource.com/chromium/src/+/478c83ce79be0f8f41911bfb41840156af6d8a68 (LayoutTests, devtools: allow creating and testing OOPIFs. by pfeldman@chromium.org)
If this is incorrect, please apply the Test-Predator-Wrong-CLs label.

Automatically adding ccs based on suspected regression changelists:

https://chromium.googlesource.com/chromium/src/+/16289b3ef759d892a4058671e0657c016101be23 (Use C++11 alignment primitives by brettw@chromium.org)https://chromium.googlesource.com/chromium/src/+/478c83ce79be0f8f41911bfb41840156af6d8a68 (LayoutTests, devtools: allow creating and testing OOPIFs. by pfeldman@chromium.org)
If this is incorrect, please apply the Test-Predator-Wrong-CLs label.

Please ignore the Test-Predator-Auto-CC comment spam above, there was a bug in our script that caused it to create same comment multiple times and also didn't add ccs properly. 

 Issue 767023  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 537260:537261.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x117e3aeb0580
Crash State:
  Bad-cast to blink::WebView from invalid vptr
  test_runner::TestRunnerForSpecificView::Reset
  test_runner::WebViewTestProxyBase::Reset
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=479114:479272
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=537260:537261

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

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

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot