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 assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/68aabd926591afe79a3aa464ebb3eba038295b73 (Identify PDF file being printed by checking URL).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

I don't think it was due to my CL as my change is only on the browser side. But this crash happens in the renderer. 

ClusterFuzz seems a bit confused about this bug, plus it's not clear that it's a bug in production code (crash is in test code). I'll try to reproduce later tonight and see if I can figure out what's going on.

I can't reproduce locally, but I suspect this is a duplicate (and not a security bug because it's test code on the call stack).

ClusterFuzz has detected this issue as fixed in range 545879:545880.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x06d1b1ab0280
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=542629:542630
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=545879:545880

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

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.