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/+/523efae2ae9590d0bc4c0229277020db49fb5438 (Field Trial: Drop runtime flag for V8ContextSnapshot).

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.

ClusterFuzz has detected this issue as fixed in range 617060:617061.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900009495
Crash State:
  blink::ReportFatalErrorInMainThread
  v8::Utils::ReportApiFailure
  ApiCheck
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=616191:616192
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=617060:617061

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

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

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