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

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

Possibly a dup of  issue 912433 

Sorry for the unminimized testcases. 
I will post a smaller one if possible.

ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://clusterfuzz.com/testcase?key=5156477393960960.

ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://clusterfuzz.com/testcase?key=5095333333565440.

capn, could you take this SwiftShader issue?

Definitely looks like a duplicate of  Issue 912433 , just for another Subzero instruction being appended.

ClusterFuzz has detected this issue as fixed in range 624266:624267.

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

Fuzzer: metzman_graphicsfuzz_crash_fuzzer
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000020
Crash State:
  Ice::CfgNode::appendInst
  rr::Nucleus::createLoad
  rr::Float4::operator=
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=543343:543344
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=624266:624267

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.