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

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

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

https://chromium.googlesource.com/chromium/src/+/cd81d2e64ffd7f6cace01432abe8b59b978914cd%5E%21/ in the regression range fixes blacklisting for files named lifecycle_observer. It shouldn't be the CL that introduced the bug, but then again I don't see anything that might be relevant either.

tkent: Could you please take a look as the author of that CL?

TestRunnerForSpecificView is not production code.
Yes, my CL can't cause this issue. But I'll take a look at this as a code owner.

I couldn't reproduce this locally.

Downgrading to P3 because of the reason given in #7: TestRunnerForSpecificView is not production code

ClusterFuzz has detected this issue as fixed in range 602138:602139.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x2d221da98500
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=549412:549420
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=602138:602139

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

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

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