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/+/4ea14eb904e6d48aab3b9d635176e49c5fd68f3e ([run_web_tests] Remove --pixel-test/--pixel-tests option).

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.

This is not new, but clusterfuzz found it after my CL which enabled pixel dumping by default. If clusterfuzz used --pixel-test option then it could reproduce the issue without my CL.

WontFix because it happens in a particularly written layout test only and I'd not put effort on it. It doesn't affect production.

ClusterFuzz has detected this issue as fixed in range 604097:604098.

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

Fuzzer: inferno_twister_c
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  render_view()->GetWebView()->IsAcceleratedCompositingActive() in blink_test_runn
  content::BlinkTestRunner::CaptureLocalPixelsDump
  content::BlinkTestRunner::TestFinished
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=602138:602139
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=604097:604098

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

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.