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/v8/v8/+/b2abe2cf971a382e973a9e99124452a9bfe2005a ([wasm] Introduce specialized WasmCompileLazy frame type.).

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 53411:53412.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_msan_d8
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  v8::internal::MarkCompactCollector::RootMarkingVisitor::VisitRootPointers
  v8::internal::WasmCompileLazyFrame::Iterate
  v8::internal::Isolate::Iterate
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_d8&range=53404:53405
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_d8&range=53411:53412

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

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

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