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

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

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "abort.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/32f4f17b0e36495c371498e1168b736fce87f289

kaiwang@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

***Correction***

Unable to assign to kaiwang@, hence assigned to reviewer.

ClusterFuzz has detected this issue as fixed in range 618343:618353.

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

Fuzzer: metzman_graphicsfuzz_crash_fuzzer
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000039
Crash State:
  tcmalloc::Abort
  tcmalloc::Log
  do_malloc
  
Sanitizer: undefined (UBSAN)

Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=618343:618353

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

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.

ClusterFuzz testcase 5067516004794368 is verified as fixed, so closing issue as verified.

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