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

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

Max, this looks like the thing you fixed yesterday. Can you verify?

ClusterFuzz has detected this issue as fixed in range 525123:525236.

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

Fuzzer: libFuzzer_v8_wasm_globals_section_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  v8_fuzzer::FuzzerSupport::GetIsolate
  v8::internal::wasm::fuzzer::FuzzWasmSection
  start
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=493100:493156
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=525123:525236

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 5883894506455040 is verified as fixed, so closing issue as verified.

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

Yes, looks fixed now.